Method and system for multi-modal transaction authentication

ABSTRACT

This invention relates to systems and methods for authenticating transactions using a mobile device based primarily on the introduction of a layer of middleware and wherein the Payment Networks, Merchants, Issuing Banks, Credit Reporting Bureaus, Insurance Companies, Healthcare Providers may customize the implementation of the services based on individual strategy and consumer preferences.

RELATED APPLICATIONS AND PRIORITY CLAIM

The present application is a continuation application of and claimspriority to U.S. patent application Ser. No. 15/827,606, filed Nov. 30,2017, and titled “Method and System For Multi-Modal TransactionAuthentication,” which is a continuation application of and claimspriority to U.S. patent application Ser. No. 14/581,471, filed Dec. 23,2014, and titled “Method and System for Secure Transactions,” which isnow U.S. Pat. No. 9,852,426 issued Dec. 26, 2017, which is acontinuation-in-part of and claims priority to U.S. patent applicationSer. No. 14/035,160, filed Sep. 24, 2013, and titled “Method and Systemfor Securing Payment Transactions,” which is now U.S. Pat. No. 9,159,061issued Oct. 13, 2015, which is a continuation application of and claimspriority to U.S. patent application Ser. No. 12/390,003, filed Feb. 20,2009, and titled “Method and System for Securing Payment Transactions,”which is now U.S. Pat. No. 8,577,804 issued Nov. 5, 2013, and whichclaims the benefit of priority of the following U.S. provisionalapplications:

Application No. Filed On Title 61/066,416 Feb. 20, 2008 Method forSecuring PIN Debit Transactions on the Internet 61/050,724 May 6, 2008Method for Securing PIN Debit Transactions on the Internet 61/130,306May 29, 2008 Method for Securing PIN Debit Transactions on the Internet61/190,743 Sep. 2, 2008 Method for Securing PIN Debit Transactions onthe Internet 61/191,293 Sep. 8, 2008 Method for Securing PIN DebitTransactions on the InternetThe content of the foregoing applications is hereby fully incorporatedherein by reference.

U.S. patent application Ser. No. 14/581,471, filed Dec. 23, 2014, andtitled “Method and System for Secure Transactions,” also claims priorityto U.S. Provisional Patent Application No. 61/921,758, filed on Dec. 30,2013, and titled “Method and System for Securing Payment Transactions”;and claims priority to U.S. Provisional Patent Application No.62/006,449, filed on Jun. 2, 2014, and titled “Method and System forSecuring Payment Transactions”. The content of the foregoingapplications is hereby fully incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document may contain materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor patent disclosure as it appears in the U.S. Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

This invention relates to systems and methods for authenticatingtransactions using a mobile device.

BACKGROUND OF THE INVENTION

There are two primary types of debit cards in use today for consumerpurchases in the US: signature debit and PIN debit. The following is abrief overview of each:

A signature debit card typically carries a Visa or MasterCard brand andis generally accepted as a form of payment at any location that acceptsthe Visa or MasterCard Credit Cards. These Signature Debit transactionsutilize the infrastructure provided by the major Credit Card networks(such as Visa, MasterCard) and utilize a two-step process which includesan authorization step followed by a settlement step. Signature debitcards issued from the major networks are accepted at the vast majorityof physical merchants and eCommerce merchants. No special equipment isrequired for merchants to accept signature-debit cards beyond theequipment already in place to process credit cards; however, a signaturefrom the cardholder is required. Conversely, signatures are neithersupported nor required for online purchases made with thesesignature-debit cards. As a result of the increased potential for fraud,online merchants pay a higher fee for accepting these “card not present”transactions.

A PIN Debit card payment transaction, by contrast, presently requires aspecial type of equipment that is used to securely capture and store thecardholder personal identifying number (“PIN”). A PIN is typically astring of numbers and/or other characters that serve as a confidentialcode associated with a cardholder's account. An encrypted PIN pad isattached to the merchant's point of sale (“POS”) terminal. Whenprompted, the cardholder enters the secret PIN using the encrypted PINpad. Using the hardware, CPU and circuitry of the encrypted PIN pad, thecardholder PIN number is then encrypted and stored as a field (e.g. PINBlock) within a record of the payment transaction. PIN Debittransactions are received and processed by the debit networks usingproprietary systems which are physically different and separate from thesignature debit networks. PIN Debit cards carry the advantages ofadditional security for cardholders and lower fraud and acceptance costsfor merchants. However, because of the requirement to securely captureand store the cardholder PIN number, PIN Debit has not been broadlyadopted for online, eCommerce sales, such as those conducted via theInternet.

So, whereas signature debit is widely accepted and used in connectionwith eCommerce sales, PIN-based debit does not enjoy the same level ofacceptance. There is little penetration of the PIN-Debit payment methodfor eCommerce sales as a result of PIN-Debit Network rules, concernsabout the protection of the cardholder PIN, and limitations related tothe current payment-processing methods. These factors combine to make itproblematic to easily allow an Internet merchant to accept a PIN-DebitCard as a form of payment. In order to overcome these limitations of thecurrent art, the present invention relates to methods and systems forenabling the broad use of PIN Debit as a payment method for secureInternet “eCommerce” sales.

Consumer research indicates that many cardholders prefer to usePIN-based debit over other forms of payment. As the cost of paymentacceptance continues to rise, fraud related to eCommerce transactions isalso a growing concern for online merchants, acquirers, and issuers.Online merchants would benefit from lower fraud and lower acceptancecosts related to the PIN-based Debit form of electronic payments.However, as a result of limitations in methods surrounding the use andprotection of cardholder PINs this payment type is not widely acceptedfor eCommerce. As consumer spending shifts away from the physical pointof sale to the Internet, the PIN-Debit networks are at risk of losingmarket share and relevance to consumers and merchants alike.

Another emerging payment trend is related to the expected growth ofmobile payments at the physical point of sale whereby the cardholderuses a “mobile wallet” in lieu of a physical wallet to digitally storeand access payment instruments from a PDA or mobile phone. As witheCommerce sales, security requirements surrounding the protection of thecardholder's Debit Card PIN number, are likely to slow down or preventthe widespread use of PIN-Debit from mobile wallet payments.Furthermore, because banks prefer the more profitable signature paymentmethods the card issuing banks may not encourage PIN-Debit to besupported in bank-approved mobile wallets. If not addressed now, thesetrends represent a potential for significant erosion of transactionvolumes for the PIN-Debit networks.

Rules regarding PIN-Debit transactions are governed by the majordomestic PIN-Debit networks (e.g. PULSE, Star, NYCE, Accel-Exchange,Shazam). Although rules vary somewhat between networks, the networks arein agreement with respect to the need for high security over thepersonal identification number or PIN. In order to protect these PINnumbers from accidental or malicious disclosure, stringenthardware-based encryption is mandated at the point-of-sale locationsthat accept these PIN-based Debit cards. After entry, the cardholder'sPIN number is encrypted and securely stored within an Encrypted PINBlock (EPB) within the payment transaction record. This cardholder PINnumber is herein referred to as the “Physical PIN”. Because of a lack ofadequate security measures for protecting the Physical PIN in eCommercetransactions, network rules generally prohibit the use of PIN-Debitcards for general eCommerce sales.

Furthermore, because the typical data set accepted by a merchant'seCommerce site is different from the data set that a PIN-Debit Networkwould typically receive from a physical point-of-sale device, asignificant amount of change is required in order to facilitate thewidespread use of PIN-Debit for eCommerce sales.

Examples of the state of the prior art for processing eCommerce andpoint-of-sale (POS) transactions are illustrated in FIGS. 1 and 2.Referring to FIG. 1, a Cardholder (1.0), sits at a PC and entersCardholder Data (1.0.1) required by the Merchant Shopping Cart (1.1).Cardholder Data typically includes the Primary Account Number (PAN),name, address, email address, ship to address and other related fields.Most merchant Shopping carts also require the entry of the CVV2 securitycode along with other Cardholder Data. Its method consists of requiringa cardholder to enter the CVV2 number in at transaction time to verifythat the card is on hand. The CVV2 code is a security feature for “cardnot present” transactions (e.g., Internet transactions), and now appearson most (but not all) major credit and debit cards. According toWikipedia “The CVV2 is a 3- or 4-digit value printed on the card orsignature strip, but not encoded on the magnetic stripe”.

The Merchant Shopping Cart (1.1) and underlying payment software aresoftware typically hosted by the Merchant in connection with itswebsite. The Merchant Shopping Cart (1.1) and payment software formatthe payment transaction and forward the payment transaction includingthe cardholder data (1.1.1) to the Gateway or Acquirer (1.2). TheGateway is defined herein as an intermediary that is often involved inprocessing eCommerce payment transactions. The Gateway can connect theMerchant to the Acquirer. The Gateway may also provide value addedservices such as fraud controls, support for recurring payments, onlinereporting, and virtual terminal data entry. The Gateway ultimatelyforwards the transaction to the Acquirer. The Acquirer typically has acontractual relationship with the Merchant for the purpose of processingpayment transactions and deposits the net proceeds for each day's salesinto the Merchant bank account. In some cases a single entity servesboth the role of Gateway and Acquirer.

The Acquirer (1.2) reformats the record comprising the transaction inaccordance with network requirements and forwards the ISO 8583 (1.3)formatted transaction to the Credit Card Networks (1.4). For definitionpurposes, and according to the Wikipedia, “The vast majority oftransactions made at Automated Teller Machines use ISO 8583 at somepoint in the communication chain, as do transactions made when acustomer uses a card to make a payment in a store. In particular, boththe MasterCard and Visa networks base their authorization communicationson the ISO 8583 standard, as do many other institutions and networks.Cardholder-originated transactions include purchase, withdrawal,deposit, refund, reversal, balance inquiry, payments and inter-accounttransfers. ISO 8583 also defines system-to-system messages for securekey exchanges, reconciliation of totals, and other administrativepurposes. Although ISO 8583 defines a common standard, it is nottypically used directly by systems or networks. Instead, each networkadapts the standard for its own use with custom fields and customusages”.

The Credit Card Network (1.4) receives the ISO 8583 payment transactionand forwards it (1.4.1) to the card issuing bank or Issuer (1.5). TheIssuer determines whether the cardholder has sufficient credit oravailable funds to complete the purchase and sends a response message(1.5.1) back to the Card Network (1.4). The transaction path istraversed until the response message is received by the Merchant. Asshown by element 1.4, the PIN Debit Networks are not represented in thelist of available networks for credit card and signature debit paymentacceptance. This is primarily a result of the fact that the prior artdoes not support the secure entry of Physical PIN numbers into MerchantShopping carts without requiring significant changes to the existingnetworks.

FIG. 2.0 illustrates prior art for processing payment transactions atthe physical point-of-sale (POS), as opposed to an on-line transactionas illustrated in FIG. 1. Referring to FIG. 2, a Cardholder (1.0) uses aphysical card that provides data (2.0.1), typically via a magneticstrip, to the Merchant POS System (2.1). The Merchant POS System readsthe data from the card and determines from the Primary Account Number(PAN) that the card is related to a PIN Debit Network and then promptsthe Cardholder (1.0) to enter the Physical PIN (2.0.2) into the PIN Pad(2.1.1). The Physical PIN Number is encrypted by the PIN Pad and passedto the Merchant POS System for insertion into the payment transactionEncrypted PIN Block. The Merchant POS System (2.1) forwards the PaymentTransaction including the cardholder data (2.1.1) and the Encrypted PINBlock (2.1.2) to the Acquirer (2.2).

The Acquirer further formats the transaction and forwards the ISO 8583transaction (2.3) to the Debit Network (2.4). These Debit Networksinclude organizations such as (STAR, PULSE, NYCE) and others. The DebitNetwork (2.4) forwards the transaction (2.4.1) to the Issuer (2.5). TheIssuer determines if there is sufficient funding available in thecardholder's account, validates the Physical PIN and returns a responsecode (2.5.1) to the POS.

It is important to note that this prior art does not support the entryof data elements into the Merchant POS System (2.1) that would becommonly supported by the Merchant Shopping Cart shown in FIG. 1.1). Thedata elements which are not supported include such information as:Cardholder address, CVV2 security code, email address, and other datatypically required for eCommerce transactions.

As has been described above, there are differences in the systems,requirements and methods that are currently used to process onlineSignature Debit and POS based PIN-Debit payments. There are alsodifferences in the formatted ISO 8583 transactions. The most notabledifferences being that the POS PIN-Debit transaction (2.1.1) includesthe Encrypted PIN Block and the eCommerce transaction (1.1.1) includesthe CVV2, cardholder address, and other data fields and specificallydoes not support the EPB.

In order to promote the use of PIN Debit for ecommerce sales, methodsand systems have been proposed and developed with limited success. Newmethods have failed to attract cardholders, merchants, or networks as aresult of their limitations. For example:

(i) Some current methods require the cardholder to install specialsoftware on their personal computer.

(ii) Other methods require the cardholder to purchase and, or installspecial equipment such as PIN pads or magnetic-stripe readers onpersonal computers.

(iii) Other methods require the cardholder to leave the merchant'seCommerce site when using the PIN-Debit payment method.

(iv) Still other methods require significant changes to merchant sites,transaction formats, and issuer authorization methods.

The widespread adoption of PIN-Debit payments for eCommerce transactionswill be facilitated if the PIN can be securely processed in a simplermanner for the cardholders, merchants, payment gateways, networks, andissuing banks or their processors. Therefore, a need exists for a methodwhich will overcome current limitations and lead to the widespreadacceptance of PIN-Debit transactions for eCommerce (Internet Sales).

Another emerging risk for PIN-Debit Networks is related to the expectedgrowth of mobile payments at the physical point-of-sale and for onlinepayments. A mobile payment is best characterized as a payment made to amerchant that is facilitated by a payment instrument digitally stored ina mobile wallet. As in the case of a payment made at the physical pointof sale, at checkout the cardholder is prompted by the mobile walletapplication to select a payment method from among the cardholder'spreviously-stored payment instruments (e.g. credit card, signaturedebit, prepaid or gift card). The mobile wallet then prompts thecardholder to enter a “mobile wallet PIN number” and subsequentlyreleases the selected payment type to the acquiring processor forauthorization and settlement. Because PIN-Debit transactions made at thepoint of sale require an encrypted PIN pad for completion, using currentmethods, a PIN-Debit transaction would require a second Physical PINnumber to be entered into the available POSPIN pad. Although possible,the entry of two PIN numbers for a single point-of-sale transactionwould be considered slow and inefficient while detracting from the“mobile payment experience”. Therefore, a method is needed that willenable the PIN-Debit payment to be supported by mobile wallet paymentsin such a way as to require only the “mobile wallet PIN number” to beentered by the cardholder.

SUMMARY OF THE INVENTION

The invention satisfies the above-described and other needs by providingsystems and methods for processing eCommerce, Mobile, and point-of-salepurchases. The systems and methods described herein allow for processingPIN-debit transactions without significant modifications of existingDebit Networks, point-of-sale equipment, or eCommerce transaction sitessuch as websites. The systems and methods described herein also allowfor the authentication of non-payment transactions using a mobiledevice.

In one exemplary embodiment, the invention provides a method forprocessing PIN-debit payments received at a web site operated by amerchant. The merchant can receive the customer's account number andforward it to an acquirer computing device that determines whether thetransaction is a PIN-debit transaction. If the transaction is aPIN-debit transaction, the acquirer computing device can forward theaccount number to a PIN-debit service computing device for processing.The PIN-debit service computing device can communicate with the customervia the customer's mobile telephone to obtain approval for thetransaction. The PIN-debit service computing device can also insert thecardholder's Physical PIN associated with the PIN-debit account numberand forward the transaction with the cardholder PIN to a Debit Networkfor processing.

In another exemplary embodiment, the invention provides a system forprocessing PIN-debit payments received at a website operated by amerchant. An acquirer computing device can receive a transaction recordcomprising a customer account number from the merchant. The acquirercomputing device can determine whether the transaction record representsa PIN-debit transaction and, if so, forward the transaction record to aPIN-debit service computing device for processing. The PIN-debit servicecomputing device can communicate with the customer via a mobiletelephone to obtain authorization for the transaction. The PIN-debitservice computing device can also insert into the transaction record thecardholder's Physical PIN associated with the account number and forwardthe augmented transaction record to a Debit Network for processing.

In yet another exemplary embodiment, the invention comprises a methodfor processing a PIN-debit transaction at a point-of-sale. Apoint-of-sale device can receive a cardholder's mobile payment accountnumber from the cardholder's mobile telephone and forward the mobilepayment account number in a transaction record to an acquirer forprocessing. The acquirer can forward the transaction record with themobile payment account number to a PIN-debit service computing devicewhich comprises a mobile wallet system. The mobile wallet system canrequest a payment method from the customer via the cardholder's mobiletelephone. If the cardholder selects a PIN-debit payment method, thePIN-debit service computing device can exchange the mobile accountnumber with the cardholder's primary debit account number and insert thecardholder's associated personal identification character string intothe payment transaction. The PIN-debit service computing device can alsoforward the augmented transaction record including the personalidentification string to a Debit Network for processing.

In yet another embodiment, the invention comprises a system forprocessing a PIN-debit transaction at a point-of-sale. The systemcomprises a point-of-sale device operable to receive a cardholder'smobile payment account number from a mobile telephone and to forward themobile payment account number in a transaction record to an acquirer forrouting to a PIN-debit service computing device. The PIN-debit servicecomputing device can comprise a mobile wallet system for communicatingwith the cardholder's mobile telephone and obtaining a payment selectionmethod from the cardholder. If the cardholder selects a PIN-debitpayment method, the PIN-debit service computing device can substitutethe cardholder's primary debit account number for the mobile accountnumber and add the cardholder's personal identification character stringto the transaction record. Once the transaction record has been updated,the PIN-debit service computing device can forward the transactionrecord to a Debit Network for processing.

In yet another embodiment, the invention comprises a system forprocessing a payment transaction at a merchant Shopping cart. The systemcomprises a merchant Shopping cart device operable to receive acardholder's mobile payment account number from a mobile telephone andto forward the mobile payment account number in a transaction record toan acquirer for routing to a Mobile Wallet & PIN-debit service computingdevice. The Mobile Wallet & PIN-debit service computing device cancomprise a mobile wallet system for communicating with the cardholder'smobile telephone and obtaining a payment selection method from thecardholder. If the cardholder selects a PIN-debit payment method, thePIN-debit service computing device can substitute the cardholder'sprimary debit account number for the mobile account number and add thecardholder's personal identification character string to the transactionrecord. If the cardholder selects a payment method other than PIN-debitpayment method, the Mobile Wallet & PIN-debit service computing devicecan substitute the cardholder's primary account number for the mobileaccount number. Once the transaction record has been updated, the MobileWallet & PIN-debit service computing device can forward the transactionrecord to a Credit Card Network, Debit Card Network or alternate paymentnetwork for processing.

In another exemplary embodiment a mobile device can be used to approvethe release of a credit report using a mobile device.

In another exemplary embodiment a mobile device can be used to approvethe release of a medical record using a mobile device.

In another exemplary embodiment a user interface allows PIN numbers andbiometric factors to be collected simultaneously by a user interface onthe device.

In another exemplary embodiment a single payment transaction can besplit into multiple account numbers based on one or more of location,SIC code, and UPC code.

In another exemplary embodiment, multiple mobile registered devices maybe required to authenticate a single transaction.

The foregoing exemplary embodiments and other embodiments will bediscussed in greater detail in the Detailed Description in connectionwith the attached drawings illustrating the best mode for carrying outthe invention as presently perceived.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an overview of a conventional eCommerce transaction.

FIG. 2 illustrates an overview of a conventional point-of-saletransaction.

FIG. 3 illustrates an eCommerce transaction in accordance with anexemplary embodiment of the invention.

FIG. 4 illustrates a point-of-sale transaction in accordance with anexemplary embodiment of the invention.

FIG. 5 illustrates an architecture for receiving and storing DebitNetwork configuration settings in accordance with an exemplaryembodiment of the invention.

FIG. 6 illustrates an architecture for receiving and storing issuerconfiguration settings in accordance with an exemplary embodiment of theinvention.

FIG. 7 illustrates an architecture for receiving and storing card holderconfiguration settings in accordance with an exemplary embodiment of theinvention.

FIG. 8 illustrates an architecture for receiving and storing merchantconfiguration settings in accordance with an exemplary embodiment of theinvention.

FIG. 9 illustrates an architecture for receiving and storing gateway andacquirer configuration settings in accordance with an exemplaryembodiment of the invention.

FIG. 10 illustrates an architecture for receiving and storing processorconfiguration settings in accordance with an exemplary embodiment of theinvention.

FIG. 11 illustrates the data flow for an eCommerce transaction inaccordance with an exemplary embodiment of the invention.

FIG. 12 illustrates the data flow for a point-of-sale transaction inaccordance with an exemplary embodiment of the invention.

FIG. 13 illustrates in greater detail the data flow for an eCommercetransaction in accordance with an exemplary embodiment of the invention.

FIG. 14 illustrates in greater detail the processing of payments usingconfiguration settings for an eCommerce transaction in accordance withan exemplary embodiment of the invention.

FIG. 15 illustrates in greater detail the augmenting of payment data foran eCommerce transaction in accordance with an exemplary embodiment ofthe invention.

FIG. 16 illustrates in greater detail the primary components of thesecure PIN Debit computing device in accordance with an exemplaryembodiment of the invention.

FIG. 17 illustrates the data flow for an internet transaction inaccordance with an exemplary embodiment of the invention.

FIG. 18 illustrates an architecture for a computing device in accordancewith an exemplary embodiment of the invention.

FIG. 19 illustrates an architecture for enhanced POS security.

FIG. 20 illustrates an architecture for enhanced ATM security.

FIG. 21 illustrates an architecture for enhanced eCommerce security.

FIG. 22 illustrates a standard POS payment flow using a mobile PAN.

FIG. 23 illustrates an alternate standard POS payment flow using amobile PAN.

FIG. 24 illustrates an enhanced POS payment flow using a mobile PAN.

FIG. 24R illustrates a reverse POS payment flow using a mobile PAN.

FIG. 25 illustrates an alternate enhanced POS payment flow using amobile PAN.

FIG. 26 illustrates a standard POS payment flow using a credit or debitcard.

FIG. 27 illustrates an alternate standard POS payment flow using acredit or debit card.

FIG. 28 illustrates an enhanced POS payment flow using a credit or debitcard.

FIG. 29 illustrates an alternate enhanced POS payment flow using amobile PAN.

FIG. 30 illustrates a standard eCommerce payment flow using a mobilePAN.

FIG. 31 illustrates an alternate standard eCommerce payment flow using amobile PAN.

FIG. 32 illustrates an enhanced eCommerce payment flow using a mobilePAN.

FIG. 32R illustrates a reverse eCommerce payment flow using a mobilePAN.

FIG. 33 illustrates an alternate enhanced POS payment flow using amobile PAN.

FIG. 34 illustrates a standard ATM transaction flow using a mobile PAN.

FIG. 35 illustrates an alternate standard ATM transaction flow using amobile PAN.

FIG. 36 illustrates an enhanced ATM transaction flow using a mobile PAN.

FIG. 36R illustrates a reverse ATM transaction flow using a mobile PAN.

FIG. 37 illustrates an alternate enhanced ATM transaction flow using amobile PAN.

FIG. 38 illustrates a standard ATM transaction flow using a credit ordebit card.

FIG. 39 illustrates an alternate standard ATM transaction flow using acredit or debit card.

FIG. 40 illustrates an enhanced ATM transaction flow using a credit ordebit card.

FIG. 41 illustrates an alternate enhanced ATM transaction flow using acredit or debit card.

FIG. 42 illustrates a registered cards and accounts table.

FIG. 43 illustrates a registered users table.

FIG. 44 illustrates a registered users, cards, and PINs table.

FIG. 45 illustrates a registered users, locations table.

FIG. 46 illustrates a registered cards, locations table.

FIG. 47 illustrates a registered locations table.

FIG. 48 illustrates a registered devices table.

FIG. 49 illustrates a user's devices table.

FIG. 50 illustrates a device, device PIN, token table.

FIG. 51 illustrates a user, PIN table.

FIG. 52 illustrates a card, mobile PIN table.

FIG. 53 illustrates a card, device table.

FIG. 54 illustrates a registered merchant table.

FIG. 55 illustrates a registered merchant, location, terminal table.

FIG. 56 illustrates a mobile Pan, mobile PIN, Mobile Pan token table.

FIG. 57 illustrates a mobile Pan, Card No., selection table.

FIG. 58 illustrates a entity approval criteria table.

FIG. 59 illustrates a dynamic card selection table.

FIG. 60 illustrates a Dynamic PIN card selection table.

FIG. 61 illustrates a venue, biometric table.

FIG. 62 illustrates a PIN, biometric correlation table.

FIG. 63 illustrates the key entry user interface needed to accommodatethe collection of biometric factors in combination with PIN numbers.

FIG. 64 illustrates a payment account registration process sponsored bythe merchant.

FIG. 65 illustrates a payment account registration process sponsored bythe payment account issuer.

FIG. 66 illustrates an account registration process initiated by theconsumer.

FIG. 67 illustrates an account registration process sponsored by aninsurance company.

FIG. 68 illustrates an account registration process sponsored by acredit reporting agency.

FIG. 69 is an exemplary use case whereby a mobile authentication isrequired in order to release a credit report.

FIG. 70 is an exemplary use case whereby a mobile authentication isrequired in order to release a medical record.

FIG. 71 is a second exemplary use case whereby a mobile authenticationis required in order to release a medical record.

FIG. 72 describes the algorithm used to decode a dynamic Mobile PANnumber.

FIG. 73 describes the ecosystem and registered participants.

FIG. 74 describes the common authentication steps for payment andnon-payment transactions.

FIG. 75 illustrates a biometric device hub in accordance with an exampleembodiment of the disclosure.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

The present invention answers these needs by providing a method forenabling the broad use of the PIN-Debit payment method for eCommerce andMobile Wallet sales without requiring the cardholder to purchase orinstall special software or hardware on their PC, without requiring themerchant to make extensive changes to their eCommerce sites and withoutrequiring the payment gateways, Debit Networks, card issuers or otherstakeholders to make significant changes to their transactionauthorization and settlement processes. The present invention alsoallows the participants to share a common infrastructure provided by theSecure PIN Debit Service (SPDS) for processing eCommerce and MobileWallet transactions while providing a basis for competitivedifferentiation.

In embodiments of the present invention as illustrated in FIG. 5.0 eachparticipating Debit Network will independently define and maintain a setof unique rules, preferences and settings which will serve as the“configuration settings” for the Debit Network. Configuration settingswill be used by the SPDS to govern key aspects of transactionprocessing, define allowable card issuer functions and feature sets, anddetermine allowable cardholder functions and features while providing abasis for competitive differentiation. These settings are securelyentered, displayed, and updated by authorized representatives of theDebit Network (5.1) using Terminal (5.1.0) to create or updateConfiguration Settings (5.1.1). At a minimum these settings would definethe specific message format that the Debit Network mandates for paymenttransactions. Configuration Settings could also specify, for example,the type of merchants that are authorized to utilize the payment methodas represented by the merchant's Standard Industrial Classification Code(SIC), Merchant Classification Code (MCC) code or other similardesignation. Other configuration settings will relate to the specificmethod by which the Debit Network handles key encryption and otherproprietary aspects of processing or message formats which woulddifferentiate one Debit Network's (5.1) transaction processingrequirements from another (e.g. 5.2). Still other configuration settingsmay relate to specific feature sets that the Debit Network will requireor allow Issuers to implement. For example, Debit Network (5.1) maymandate that all cardholder transactions over a specific dollar amountrequire a secondary cardholder authorization based on an emailnotification while Debit Network (5.2) may allow issuers to make thisdetermination.

In other embodiments of the present invention as illustrated in FIG.6.0, within the framework allowed by each Debit Network as specified inthe Debit Network Configuration Settings, each participating DebitIssuer will independently define and maintain a set of unique rules,preferences and settings which will serve as the “Issuer Settings”.Issuer settings will be used by the SPDS to govern key aspects oftransaction processing, define the issuing bank's unique set ofcardholder functions and features and provide a basis for competitivedifferentiation. These settings are securely entered, displayed, andupdated by authorized representatives of the Debit Issuer (6.1) usingTerminal (6.1.0) to create or update Issuer Settings (6.1.1). As shown,the set of Debit Issuer settings that are allowable are governed firstand foremost by the Debit Network Configuration Settings. As shown forpurpose of illustration Issuer Settings (6.1.1) are governed by DebitNetwork Settings (5.1.1) and Issuer Settings (6.3.1) are governed byDebit Network Settings (5.3.1). Issuer Configuration Settings specify,for example, the type of merchants that are authorized to utilize thePIN Debit payment method as represented by the merchant's StandardIndustrial Classification Code (SIC), Merchant Classification Code (MCC)code or other similar designation. Other configuration settings willrelate to the features that the Issuer wishes to make available to itsDebit Cardholders. These settings may allow Cardholders to registerMobile Phone Number, specify standards for Mobile PIN Numbers, enablefeatures that allow Debit Cardholders to create lists of approved orprohibited merchants, specify daily transaction limits, and othersimilar features. Finally, Debit Issuer settings will specify to theSPDS the specific method with which to obtain and protect theirCardholder's Physical PIN Number and the specific method with which toaugment ISO 8583 payment transactions with the Encrypted PIN Block asdiscussed further in FIG. 15.

In other embodiments of the present invention as illustrated in FIG.7.0, within the framework allowed by each Debit Issuer as specified inthe Issuer Settings, each participating cardholder will independentlydefine and maintain a set of unique rules, preferences and settingswhich will serve as the “Cardholder Settings” for their PIN Debit cards.Cardholder settings will be used by the SPDS to govern key aspects oftransaction processing and control the behavior of cardholder's uniquefunction and feature sets. These settings are securely entered,displayed, and updated by the Debit Cardholder (7.1) using Terminal(7.1.0) to create or update Configuration Settings (7.1.1). As shown,the set of Debit Cardholder settings that are allowable are governed bythe Debit Issuer Configuration Settings. As shown for purpose ofillustration Cardholder Settings (7.1.1) are governed by Issuer Settings(6.1) and Cardholder Settings (6.3.1) are governed by Issuer Settings(6.3.1). Cardholder Configuration Settings will allow Cardholders toregister a single or multiple mobile phone numbers, specify a Mobile PINNumber based on Issuer standards, create lists of approved andprohibited merchants, specify daily transaction limits, specify primaryand secondary email accounts and enable and configure other similarfeatures which will combine to make each Debit Cardholder's experienceunique while conforming to the standards mandated by the Issuer andDebit Network.

In other embodiments of the present invention as illustrated in FIG.8.0, within the framework allowed by the governing rules established forthe SPDS, each Merchant will independently define and maintain a set ofunique rules, preferences and settings which will serve as the “MerchantSettings” related to processing PIN Debit cards. Merchant settings willbe used by the SPDS to govern key aspects of transaction processing. Asshown in FIG. 8, these settings are securely entered, displayed, andupdated by an authorized representative of the Merchant (8.1) usingTerminal (8.1.0) to create or update Merchant Settings (8.1.1). Thesesettings would include all unique identifying information about aMerchant such as: Merchant Legal Name, Merchant Address, Tax Id Number,SIC Code, MCC Code, Merchant Id., Gateway processor, Acquirer, and otherdata that will be needed to correctly process and route the Merchantpayment transactions.

In other embodiments of the present invention as illustrated in FIG.9.0, within the framework allowed by the governing rules established forthe SPDS, each Gateway and Acquirer will independently define andmaintain a set of unique rules, preferences and settings which willserve as the “Gateway Settings” and “Acquirer Settings” related toprocessing PIN Debit cards. Gateway settings will be used by the SPDS togovern key aspects of transaction processing and provide a basis forcompetitive differentiation. As shown in FIG. 9, these Gateway settingsare securely entered, displayed, and updated by an authorizedrepresentative of the Gateway (9.1) using Terminal (9.1.0) to create orupdate Gateway Settings (9.1.1). Similarly, Acquirer settings aresecurely entered, displayed, and updated by an authorized representativeof the Acquirer (9.2) using Terminal (9.2.0) to create or update GatewaySettings (9.2.1). These settings would include specific messageformatting requirements for payment transactions and specify othertransaction processing options that are available only to Merchantsusing payment processing services offered by these entities.

In other embodiments of the present invention as illustrated in FIG.10.0, within the framework allowed by the governing rules establishedfor the SPDS, each Processor will independently define and maintain aset of unique rules, preferences and settings which will serve as the“Processor Settings” related to processing PIN Debit cards. Processorsettings will be used by the SPDS to govern key aspects of transactionprocessing and provide a basis for competitive differentiation. As shownin FIG. 10, these Processor Settings are securely entered, displayed,and updated by an authorized representative of the Processor (10.1)using Terminal (10.1.0) to create or update Processor Settings (10.1.1).Processor Settings will define specific message formats for paymenttransactions, encryption requirements and other specifics related to howeach processor uniquely handles payment transactions and PINs.

In accordance with the methods described above, configuration settingscan be created for each participating Debit Network, Issuing Bank,Merchant, Processor, Gateway and Cardholder prior to use of the SPDSmethods. Prior to using the SPDS system, each cardholder first registerstheir Debit card(s) and sets options in accordance with allowable rangesas prescribed by their Issuing Bank (e.g.—Purchase limits, daily limits,cell phone numbers, email accounts, lists of approved and prohibitedmerchants, etc.). Upon successful registration and configuration, theSPDS generates a unique Mobile PIN Number using a proprietary algorithmand based on the requirements and settings established. The Mobile PINNumber is provided to the Debit Cardholder at which point the DebitCardholder makes a record of the number for subsequent use. The MobilePIN Number is associated with the Debit Card PAN and can be restrictedto use for eCommerce and Mobile Wallet purchases. An email, text message(or other suitable communication) is sent to the cardholder as anotification that the Mobile PIN Number has been generated or changed.

An embodiment of an online payment processed using an exemplary SPDS isillustrated in FIG. 3. It should be understood that in alternateembodiments of the invention the sequence of steps and entitiesperforming the steps can be varied somewhat from what is shown in FIG. 3without departing from the scope of the invention. As shown in FIG. 3,once a PIN

Debit card has been registered with the SPDS the following exemplarysequence describes the use of the registered card number for aneCommerce transaction:

(i) The cardholder makes a purchase selection at an approved Merchantweb site.

(ii) Cardholder then enters the required Cardholder Data (3.0.1) suchas: name, card number, expiration date, address, and (if required, thecvv2 field) into the Merchant Shopping Cart (3.1). The Merchant ShoppingCart (3.1) formats a Payment Transaction (3.1.1) and forwards thetransaction to the Gateway or Acquirer (3.2).

(iii) The Gateway or Acquirer (e.g. Chase, PayPal, Cybersource) acquiresthe transaction performs normal fraud and security checks includingcommon eCommerce validations such as velocity checking (e.g. tracks thevolume of payment transactions received from an IP address or paymentcard to detect possible fraud) and routes the ISO 8583 transaction(3.2.1) to the SPDS (3.3) for further processing.

(iv) The SPDS validates the transaction against the cardholder, issuer,merchant, and network rules in place. All cardholder preferences areinvoked at this point. For example, the cardholders' account can beconfigured to automatically approve or cancel purchases based on certaincharacteristics and combinations of characteristics (e.g. approved andprohibited merchant lists, transaction size, etc.).

(v) For transactions which pass the above requirements the cardholderreceives a Purchase Authentication Request communication (3.3.1) on theregistered cell phone. Upon receipt of the communication the cardholderenters the Mobile PIN (3.0.2) to approve the purchase and submits thePurchase Authentication Reply (3.4.1) which is sent back to the SPDS.

(vi) It should be noted that there are multiple methods for sending thiscommunication (3.3.1) to the phone and multiple methods for cardholderapproval using the Mobile PIN (3.0.2) some of which are addressed inembodiments herein. For example:

(vii) A computer system may dial the registered cell phone and wait forthe entry of the correct Mobile PIN number within an establishedtimeframe, or

(viii) An sms text message may be sent to the registered cell phone. Areply text message with the Mobile PIN would signify the approval of thesale, or

(ix) A secure token can be released from the cell phone upon entry ofthe Mobile PIN, or

(x) A Wireless Application Protocol (WAP) based message can be pushed tothe registered phone prompting the cardholder to enter the Mobile PIN.

(xi) Other reasonable methods as identified by the practitioner skilledin the art may be developed for the purpose of entering and protectingthe cardholder Mobile PIN and as a basis of competitive differentiation.

(xii) For those transactions which have been approved by the cardholderthe Physical PIN (Alternate PIN (e.g. a pre-established PIN that hasbeen registered with the Issuer for use only in eCommerce transactions)or a partial Physical PIN) may be inserted into the ISO 8583 transactionEncrypted PIN Block prior to routing the transaction (3.3.2) to theDebit Network (3.5). Typically, the Issuer would have registered thePhysical PIN, Alternate PIN or partial Physical PIN with the SPDS inadvance so that this step can be completed.

(xiii) Payment transactions (3.3.2) now having been augmented with thePhysical PIN, Partial PIN or Alternate PIN are routed to the DebitNetworks (3.5). Debit Networks perform all current fraud testing (e.g.neural network, stand in, etc.) on the transaction and then the DebitNetworks route the transaction (3.5.1) to the Issuer (3.6) for approval.

(xiv) The Issuer (3.6) approves or declines the transaction based onexisting capabilities and rules such as: cardholder balance, velocityand other standard validations such as daily limits, neural rules, etc.Therefore little or no change should be required of the Issuer or Issuerprocessor over current methods. However, as noted above, if a “AlternatePIN” was inserted into the transaction, the Issuer or Issuing Processorwould be required to validate this PIN as part of the process.

(xv) The issuer (3.6) then sends response code (3.6.1) typically anauthorization or decline associate with the payment transaction record(3.5.1) to the Debit Networks (3.5) which forward the response code(3.5.2) to the SPDS (3.3) which forwards the response code (3.3.3) tothe Gateway and/or Acquirer (3.2) which forwards the response code(3.2.2) to the merchant Shopping cart (3.1) and thus completing thetransaction cycle.

(xvi) The Merchant receives a response code (3.2.2) and the cardholdergets a receipt (3.1.2) and confirmation email (3.1.3) from the Merchant.As an optional step and based on the requirements of the Issuer andDebit Networks, the cardholder may also receive a confirmation email(3.3.3) from the SPDS (3.3). Upon receipt of the email, if and asallowed or required by the Issuer or Debit Network, the cardholder mayoptionally log into the web-based account (3.0.3) with their previouslyissued secret user id and password.

(xvii) After login is complete, the cardholder is presented with a listof all approved but outstanding PIN-Debit purchases waiting forsecondary approval. At this point, the cardholder can approve or cancelany or all purchases within a specified time frame.

(xviii) Depending on Debit Network Configuration, Issuer Settings andcardholder preferences, transactions may auto approve (or auto decline)within an established time window.

(xix) For approved purchases, the Merchant receives a notification ofthe approval.

This secondary notification (3.3.4) is consistent with the two-stepprocess currently in place for credit card and Signature Debittransactions where settlement typically occurs the next day aftertransaction approval.

(xx) For cardholder-cancelled or rule-cancelled purchases, a reversaltransaction is generated by the SPDS and sent to the Debit Network. Thepayment is reversed by the issuer and the Merchant does not receive thesecondary “settlement record”.

There are pros and cons related to each above method discussed relatedto the Mobile PIN Number. For example, the method of using text messagesand Mobile PIN Numbers as a basis to approve payments introduces a riskrelated to the disclosure of the unencrypted Mobile PIN Number over thewireless network. In order to provide additional protection for thecardholder's Mobile PIN Number from accidental or malicious disclosure,a number of encryption methods may be used on the mobile device.However, the use of encryption on the mobile device has the disadvantagethat it will likely require the cardholder to download an encryptionapplication which is supported and certified on mobile device. Somemobile devices may not support this application or download, thuslimiting the widespread adoption of this method. Therefore compensatingcontrols which are reflected in the overall method should be consideredcarefully in whole in securing the PIN Debit transactions.

For example, the use of a mobile phone in conjunction with acardholder's Mobile PIN Number represents a basis for dual-factorauthentication (e.g. something that the cardholder possesses andsomething that the cardholder knows). However, it may still be possiblefor fraud to occur using this method. Should the cardholder's mobilephone fall into the wrong hands and should the Mobile PIN Number also bedisclosed, a fraudulent payment could conceivably be initiated andapproved. However, the overall layered-control framework of the methoddescribed herein provides sufficient compensating controls to eitherprevent or detect this type of fraud. For example, particularly forfungible goods, the ship-to address would not be known and thetransaction would not likely pass typical address verification (AVS)controls.

Furthermore, the rules in place at the SPDS pertaining to the use of thecardholder's PAN will likely detect, flag, or prevent certaintransactions. Finally, when the cardholder has the option of logging into the SPDS and approving or declining all PIN Debit internettransactions, it makes such a fraud much more difficult by a introducingan effective “Tri-factor” layer of control for authentication.

However, in recognition of the concern addressed regarding the potentialvulnerability of the current method, we would introduce another optionalsecurity control in the form of a biometric factor. The biometric mayinclude a voice print, finger print, geometrical facial scan or otherfactor which can prove that the cardholder is engaged in the paymentprocess. Depending on the implementation method, the biometric factormay be validated either at the mobile device or a host system. However,like encryption, the ability to implement a biometric-based control willvary widely between mobile devices and implementation methods and willtherefore be limited based on the cardholder's mobile device.

The processing of unencrypted cardholder Mobile PIN Numbers fromregistered mobile phones over time will open the door to the harvestingand eventual disclosure of the Mobile PIN Number to hackers. Thedisclosed Mobile PIN Numbers in combination with the Debit Card PAN andmobile phone will allow for potential fraud. We previously discussed theuse of encryption as a method to protect the Mobile PIN Number fromaccidental or malicious disclosure. As an alternative to Mobile PINNumber encryption, the Mobile PIN Number would be used only to approvethe transaction on the mobile phone and would never be transmitted overthe wireless network. In lieu of transmitting the Mobile PIN Number, themobile phone would transmit a secure token to signify that thecardholder has approved the payment transaction. This secure token wouldbe issued to the cardholder for use on the registered handset and wouldlikely be validated by an independent, third-party token validationservice (such as VeriSign). Similar to the deployment issues related toencryption and biometrics, the ability to implement certificate ortoken-based controls will vary widely between mobile devices andimplementation will therefore be limited based on the cardholder'smobile device.

It is thus an advantage of the present invention to provide a method forwidespread acceptance of the PIN-Debit payment method without exposingthe cardholder's Physical PIN number to disclosure. The following listidentifies some of the features and benefits associated with theexemplary embodiments of the invention described herein:

Cardholder PAN is used with no need to issue special internet PAN orone-time PAN

-   -   (ii) A Mobile PIN limits fraud and does not expose the Physical        PIN    -   (iii) Mobile phone becomes the basis for dual-factor        authentication (something the cardholder has (mobile phone) and        something the cardholder knows (PIN))    -   (iv) Low impact on the Merchant, Gateway, Debit Network, Issuer        Internet Acquirer (v) Only adds one additional step in the        process to validate transaction before routing to Debit Network        and Issuer    -   (vi) Minimal or no change for issuer authentication process    -   (vii) Minimal change to merchant because in a typical eCommerce        transaction, the merchant already waits for a settlement record        to ship products, particularly for fungible products    -   (viii) Cardholders may set fraud controls for PIN Debit Card        usage on eCommerce transactions.    -   (ix) Cardholders go to a trusted, Issuer branded web site to        register cards and configure card preferences and controls in        accordance with Issuer and Debit Network tolerances.    -   (x) Leverages AVS and other common internet security controls        (velocity checking, IP, CVV etc.) for PIN Debit.    -   (xi) Provides online merchants with industry standard        functionality and fraud controls.

Many of the above described methods and controls may be used separatelyor in unique combinations to achieve the desired security level forPIN-Debit eCommerce transactions. Embodiments of the present inventionare also described further below by way of illustration.

The methods described herein for internet PIN-Debit transactions mayalso be used for Mobile Wallet payment transactions with minor changesto the described process. For example, as shown in the exemplaryembodiment illustrated in FIG. 4:

A cardholder (4.0) makes a purchase at a merchant's place of business,such as a retail store.

-   -   (ii) The Merchant POS System (4.1) or terminal is configured to        detect the Cardholder's Mobile PAN (4.4.1) using Near Field        Communications (NFC) or RFID based communications.    -   (iii) The Merchant POS System formats the payment transaction        and forwards the transaction (4.1.2) along with the Mobile PAN        to the Acquirer (4.2).    -   (iv) The Acquirer routes the transaction with Mobile PAN (4.2.1)        to the Mobile Wallet System (4.5). Elements of the Mobile Wallet        System may be located on the PDA, mobile phone or on a remote        server which is accessed by the PDA or mobile phone. The Mobile        Wallet System may physically co-located within the SPDS (4.3) or        it may be co-located at the Acquirer (4.2) or at the facility        operated by the Mobile Network Operator (e.g. AT&T, Verizon,        Sprint, etc.) The Mobile Wallet System (4.5) sends the        Cardholder a message (4.5.1) requesting the Cardholder to        specify a payment method for this purchase.    -   (v) The Cardholder selects a payment method from the previously        registered payment instruments, enters the Mobile PIN Number        (4.0.1) and submits transaction (4.4.1) to the Mobile Wallet        System (4.5).    -   (vi) If a PIN Debit Card is selected, the Mobile Wallet System        (4.5) replaces the Mobile PAN with the valid Cardholder PAN and        forwards the payment transaction (4.5.2) along with the Mobile        PIN Number to the SPDS (4.3) for processing.    -   (vii) The SPDS validates the Mobile PIN Number against the        registered Mobile PIN

Number for this Debit Card PAN and augments the payment transaction withthe Physical PIN number in the Encrypted PIN Block. [In this embodiment,the Physical PIN Number replaces the Mobile PIN Number during this step.In other embodiments, the Physical PIN number may be added to thepayment transaction as an additional data element and without replacingthe Mobile PIN number. The augmented payment transaction with EncryptedPIN Block (4.3.1) is sent back to the Mobile Wallet System (4.5)

-   -   (viii) The Mobile Wallet System (4.5) forwards the payment        transaction with Encrypted PIN Block (4.5.3) to the Acquirer.    -   (ix) The Acquirer (4.2) routes the payment transaction with        Encrypted PIN Block (4.2.2) to the appropriate Debit Network        (4.6)    -   (x) From this point in processing the transaction follows normal        payment processing flows for POS PIN Debit transactions with        little or no changes required by the Debit Networks or Issuers.    -   (xi) It is thus an advantage of the above method to facilitate        the widespread use of PIN

Debit payments from Mobile Wallet Systems without the need forsignificant changes to backend processes handled by the Debit Network(4.6) or the issuer (4.7). Other approaches to implementing the presentinvention and variations of the described embodiments may be constructedby a skilled practitioner and are considered within the scope of thepresent invention.

Embodiments of the current invention may be further explained in theexemplary embodiments illustrated in FIGS. 11, 12, 13, 14 and 15.

FIG. 11 depicts the Secure PIN Debit transaction data flow diagram.Embodiments are described as shown:

-   -   (i) The Cardholder (11.1) enters Payment Data (11.1.1) to the        Merchant Shopping Cart (11.2). Payment Data (11.1.1) typically        includes: Customer Name, Customer Address, Cardholder Name,        Cardholder Address, Card PAN, CVV2, Expiration Date, email        address, and other fields necessary to uniquely identify the        cardholder.    -   (ii) The Merchant Shopping Cart formats a payment transaction        and forwards the Payment Data (11.2.1) to the Gateway or        Acquirer (11.3). The Merchant ID and Terminal ID may be included        in the payment transaction to uniquely identify the Merchant.        The Gateway or Acquirer performs normal processing and        validations and routes the Payment Data (11.3.1) for PIN Debit        transactions to the Secure PIN Debit Service (SPDS).        Transactions that do not represent PIN-debit transactions, such        as signature debit and credit card transactions, are routed to        element (11.7).    -   (iii) The SPDS (11.4) processes the PIN Debit transaction in        accordance with all previously established Settings (11.8). For        example:        -   i. The SPDS prompts the Cardholder with message (11.4.1) to            approve the transactions.        -   ii. The Cardholder approves the transaction with message            (11.1.2)    -   (iv) The SPDS augments the payment transaction to conform to ISO        8583 POS transaction standards for POS PIN Debit Transactions        primarily through the inclusion of the Encrypted PIN Block.        Augmented Payment Data (11.4.3) is forwarded to the appropriate        Debit Network (11.5) for normal processing. In connection with        this processing, the Debit Network applies fraud rules to the        transaction and logs the transaction for billing, settlement        processing, customer service and reporting purposes.    -   (v) The Debit Network (11.5) routes the Augmented Payment Data        (11.5.1) to the Issuing Bank Processor (11.6) where the        transaction is approved or declined based on current        capabilities and methods with little or no change.    -   (vi) The Issuing Bank Processor (11.6) forwards the        Authorization or Decline message (11.6.1) to the Debit Network        (11.5).    -   (vii) From this point the transaction follows a reverse path        back to the merchant and an authorization or decline message is        provided to the merchant. If authorized, the purchase can be        completed and the cardholder is given a receipt (11.2.2).    -   (viii) For completed purchases, the Merchant Shopping Cart        (11.2) receives confirmation (11.4.6) and the cardholder (11.1)        receives confirmation (11.4.7).

FIG. 12 depicts an Alternate data flow diagram for a Mobile Secure PINDebit Transaction whereby the Mobile Wallet System and Secure PIN DebitService are combined into a single process (12.4). In this exemplaryembodiment, element (12.4) sends Payment Method Request (12.4.1) toCardholder (12.1) and Cardholder (12.1) replies with Payment MethodResponse (12.1.2) Otherwise, FIG. 12 follows a similar method to thatdescribed for FIG. 11. However, FIG. 12 is also intended to illustratethat changes in the process flow may be implemented in various ways bypractitioners who are skilled in the art without deviating from thespirit of the invention. Specifically, processes may be combined andsplit to accommodate the needs of the stakeholders and market drivenfactors.

Exemplary FIG. 13 is an expanded view of element 11.4 of FIG. 11. Asshown:

-   -   (i) Payment Data (13.0.1) is received and stored by Process        (13.1).    -   (ii) Process (13.1) forwards the Payment Data (13.1.1) to Apply        Payment Settings (13.3).    -   (iii) Apply Payment Settings (13.3) uses Configuration Settings        (13.4) to process payments in accordance with Network, Merchant,        Acquirer, Issuer, Gateway, Processor, and Cardholder preferences        as described in connection with FIGS. 5-10.    -   (iv) Apply Payment Settings sends Approval Request message        (13.3.1) to Request Approval (13.2).    -   (v) Request Approval (13.2) sends Approval Request message        (13.2.1) and receives Approval Response (13.0.2) and forwards        Approval Response (13.3.2) to Apply Payment Settings (13.3).    -   (vi) Based on the contents of Approval Response message        (13.3.2), Apply Payment Settings (13.3) augments the payment        data in accordance with settings and forwards Augmented Payment        Data (13.3.2) and receives Authorization or Decline message        (13.0.3).

Exemplary FIG. 14 is an expanded view of FIG. 13.3 which shows theprimary payment processing settings that will be applied by the SPDS.The order in which these rules are executed will vary depending on thepayment transaction and combination of settings. Steps which will befollowed for each transaction include:

-   -   (i) Apply Merchant Settings (14.1)    -   (ii) Apply Gateway Settings (14.2)    -   (iii) Apply Acquirer Settings (14.3)    -   (iv) Apply Debit Network Settings (14.4)    -   (v) Apply Processor Settings (14.5)    -   (vi) Apply Issuer Settings (14.6)    -   (vii) Apply Cardholder Settings (14.7)    -   (viii) Augment Payment Data (14.8)

FIG. 15 is an expanded view of FIG. 14.8 Augment Payment Data FlowDiagram and is specifically focused on augmentation aspects related tothe Physical PIN and Encrypted PIN Block. As shown:

-   -   (i) Payment Data (15.0.1) is received by Format ISO 8583 Message        (15.1). This process (15.1) formats the message in accordance        with the specific requirements of the Debit Network and        Processor.    -   (ii) Based on settings in place, process (15.2) inserts the        cardholder's Physical PIN (15.0.1), Partial PIN (15.0.2) or an        Alternate PIN (15.0.3) number into the Encrypted PIN Block of        the ISO 8583 payment transaction and forwards the Augmented PIN        Data (15.0.2) for further processing.

Exemplary FIG. 16 is a more detailed description of the primary elementsof the Secure PIN Debit Computing Device. Primary elements are describedas follows:

-   -   (i) Transaction Gateway (16.1)—Comprises a computing system that        contains at least the following primary embodiments (RAM, ROM,        CPU, Operating System, BIOS, System BUS, Video Adaptor, Network        Interface). The Transaction Gateway is responsible for receiving        and processing payment transactions.    -   (ii) Web Server (16.2)—Comprises a computing system that        contains at least the following primary embodiments (RAM, ROM,        CPU, Operating System, BIOS, System BUS, Video Adaptor, Network        Interface). The web server is responsible for receiving and        processing messages received from internet sources.    -   (iii) Database Server (16.3)—Comprises a computing system that        contains at least the following primary embodiments (RAM, ROM,        CPU, Operating System, BIOS, System BUS, Video Adaptor, Network        Interface). This server serves the function of controlling the        flow of inquiry and updates to system databases.    -   (iv) Messaging Server (16.4)—Comprises a computing system that        contains at least the following primary embodiments (RAM, ROM,        CPU, Operating System, BIOS, System BUS, Video Adaptor, Network        Interface). This server serves the function of communicating        with registered mobile phones and PDAs.    -   (v) Settings Database (16.5)—Comprises a data storage medium        used for the purpose of storing Merchant, Issuer, Debit Network,        Consumer, Acquirer, and Gateway settings.    -   (vi) Payments Transactions (16.6)—Comprises a data storage        device used for storing each payment transaction that is        processed by the SPDS.    -   (vii) PIN Repository (16.7)—Comprises a data storage device used        to store the Physical PIN, Alternate PIN, or Partial PIN related        to registered PIN Debit Card PANs.

FIG. 17 depicts an alternate data flow diagram for a Mobile InternetPayment Transaction whereby the combined Mobile Wallet System and SecurePIN Debit Service (17.4) can process credit card payment transactions,PIN-Debit payments, and alternative payment transactions from purchasesmade at internet Merchant Shopping Carts (17.2). In this exemplaryembodiment, Payer (17.1) provides mobile payment data (17.1.1) toMerchant Shopping Cart (17.2). Mobile payment data (17.1.1) may bemanually keyed into the Merchant Shopping Cart or it may beelectronically transmitted from a mobile phone to the Merchant ShoppingCart (17.2). In this exemplary embodiment, it is important to note thatelement (17.5) includes additional payment methods such as: PayPal(17.5.1), Google Checkout (17.5.2), Gift Cards (17.5.3), and CreditCards. Otherwise, FIG. 17 follows a similar method to that described forFIG. 11. However, FIG. 17 is also intended to illustrate that changes inthe process flow may be implemented in various ways by practitioners whoare skilled in the art without deviating from the spirit of theinvention. Specifically, new alternative payment methods may be addedwhich do not require Issuing Bank approval and may not utilizeconventional payment processing message formats such as the ISO 8583.

Although the exemplary embodiments herein are generally described in thecontext of software modules running on a computing device, those skilledin the art will recognize that the present invention also can beimplemented in conjunction with other program modules in other types ofcomputing environments. Furthermore, those skilled in the art willrecognize that the present invention may be implemented in a stand-aloneor in a distributed computing environment. In a distributed computingenvironment, program modules may be physically located in differentlocal and remote memory storage devices. Execution of the programmodules may occur locally in a stand-alone manner or remotely in aclient/server manner. Examples of such distributed computingenvironments include local area networks of an office, enterprise-widecomputer networks, and the global Internet.

The detailed description of the exemplary embodiments includes processesand symbolic representations of operations by conventional computercomponents, including processing units, memory storage devices, displaydevices and input devices. These processes and symbolic representationsare the means used by those skilled in the art of computer programmingand computer construction to most effectively convey teachings anddiscoveries to others skilled in the art. These processes and operationsmay utilize conventional computer components in a distributed computingenvironment, including remote file servers, remote computer servers, andremote memory storage devices. Each of these conventional distributedcomputing components is accessible by a processing unit via acommunications network.

The present invention includes computer hardware and software whichembody the functions described herein and illustrated in the appendedflow charts. However, it should be apparent that there could be manydifferent ways of implementing the invention in computer programming,and the invention should not be construed as limited to any one set ofcomputer program instructions. Further, a skilled programmer would beable to write such a computer program to implement the disclosedinvention without difficulty based on the flow charts and associateddescription in the application text, for example. Therefore, disclosureof a particular set of program code instructions is not considerednecessary for an adequate understanding of how to make and use theinvention. The inventive functionality of the claimed computer hardwareand software will be explained in more detail in the followingdescription in conjunction with the other figures in the application.

Referring now to FIG. 18, aspects of an exemplary computing environmentin which the present invention can operate are illustrated. Thoseskilled in the art will appreciate that FIG. 18 and the associateddiscussion are intended to provide a brief, general description of thepreferred computer hardware and program modules, and that additionalinformation is readily available in the appropriate programming manuals,user's guides, and similar publications.

FIG. 18 illustrates a conventional computing device 120 suitable forsupporting the operation of the preferred embodiment of the presentinvention. As illustrated previously in FIG. 16, the secure PIN debitcomputing device typically comprises multiple computing devices. In FIG.18, the computing device 120 operates in a networked environment withlogical connections to one or more remote computers 111. The logicalconnections between computing device 120 and remote computer 111 arerepresented by a local area network 173 and a wide area network 152.Those of ordinary skill in the art will recognize that in thisclient/server configuration, the remote computer 111 may function as afile server or computer server.

The computing device 120 includes a processing unit 121, such as“PENTIUM” microprocessors manufactured by Intel Corporation of SantaClara, Calif. The computing device 120 also includes system memory 122,including read only memory (ROM) 124 and random access memory (RAM) 125,which is connected to the processor 121 by a system bus 123. Thepreferred computing device 120 utilizes a BIOS 126, which is stored inROM 124. Those skilled in the art will recognize that the BIOS 126 is aset of basic routines that helps to transfer information betweenelements within the computing device 120. Those skilled in the art willalso appreciate that the present invention may be implemented oncomputers having other architectures, such as computers that do not usea BIOS, and those that utilize other microprocessors.

Within the computing device 120, a local hard disk drive 127 isconnected to the system bus 123 via a hard disk drive interface 132. Afloppy disk drive 128, which is used to read or write a floppy disk 129,is connected to the system bus 123 via a floppy disk drive interface133. A CD-ROM or DVD drive 130, which is used to read a CD-ROM or DVDdisk 131, is connected to the system bus 123 via a CD-ROM or DVDinterface 134. A user enters commands and information into the computingdevice 120 by using input devices, such as a keyboard 140 and/orpointing device, such as a mouse 142, which are connected to the systembus 123 via a serial port interface 146. Other types of pointing devices(not shown in FIG. 18) include track pads, track balls, pens, headtrackers, data gloves and other devices suitable for positioning acursor on a computer monitor 147. The monitor 147 or other kind ofdisplay device is connected to the system bus 123 via a video adapter148.

The remote computer 111 in this networked environment is connected to aremote memory storage device 150. This remote memory storage device 150is typically a large capacity device such as a hard disk drive, CD-ROMor DVD drive, magneto-optical drive or the like. Those skilled in theart will understand that software modules are provided to the remotecomputer 111 via computer-readable media. The computing device 120 isconnected to the remote computer by a network interface 153, which isused to communicate over the local area network 173.

In an alternative embodiment, the computing device 120 is also connectedto the remote computer 111 by a modem 154, which is used to communicateover the wide area network 152, such as the Internet. The modem 154 isconnected to the system bus 123 via the serial port interface 146. Themodem 154 also can be connected to the public switched telephone network(PSTN) or community antenna television (CATV) network. Althoughillustrated in FIG. 18 as external to the computing device 120, those ofordinary skill in the art can recognize that the modem 154 may also beinternal to the computing device 120, thus communicating directly viathe system bus 123. Connection to the remote computer 111 via both thelocal area network 173 and the wide area network 152 is not required,but merely illustrates alternative methods of providing a communicationpath between the computing device 120 and the remote computer 111.

Although other internal components of the computing device 120 are notshown, those of ordinary skill in the art will appreciate that suchcomponents and the interconnection between them are well known.Accordingly, additional details concerning the internal construction ofthe computing device 120 need not be disclosed in connection with thepresent invention.

Those skilled in the art will understand that program modules, such asan operating system 135 and other software modules 160 a, 163 a and 166a, and data are provided to the computing device 120 viacomputer-readable media. In the preferred computing device, thecomputer-readable media include the local or remote memory storagedevices, which may include the local hard disk drive 132, floppy disk129, CD-ROM or DVD 131, RAM 125, ROM 124, and the remote memory storagedevice 150.

FIG. 19 illustrates an architecture and components for enhanced POSsecurity comprised of POS device (19.1), which is further comprised ofTerminal ID (19.1.1) and Merchant ID (19.1.2). POS device may beequipped to accept traditional card payments using magnetic stripe orusing Europay MasterCard Visa (EMV) format; POS device (19.1) incommunication with Mobile Device (19.2) using Local Communication Link(19.7.1). Local Communication Link (19.7.1) may be based on an NFCcommunication protocol such as ISO 14443, Mifare or other NFC protocols.Alternatively, Local Communication Link may be based on low energy bluetooth (BLE), RFID or other protocols or optical scanning of a code suchas a QR code. Mobile Device (19.2) is further comprised of Mobile PANModule (19.2.1) and Mobile PAN (19.2.2). Mobile PAN Module (19.2.2) isfunctional to receive and store a static mobile PAN number onto MobileDevice (19.2), static mobile PAN received from Secure Payment ComputingDevice (SPCD) (19.4). Alternatively, Mobile PAN Module (19.2.1) is alsofunctional to generate a dynamic mobile PAN based on mobile PANrequirements derived from Settings (19.4.1) and using defined algorithms(see FIG. 72). Mobile Device (19.2) may be further comprised of SecureElement (19.2.4) Mobile Device (19.2) is in communication with SecurePayment Computing Device (19.4) using Mobile Communication Link(19.7.2), Network (19.3) and Host Communication Link (19.7.3). Network(19.3) may be comprised of a mobile communication network such as amobile network provided by AT&T or Verizon. Alternatively, Network(19.3) may be comprised of a local area network. In either case, Network(19.3) facilitates the communication between Mobile Device (19.2) andSecure Payment Computing Device (19.4). Geo Services (19.9) arefunctional to provide current location information to Mobile Device(19.2). Geo Services (19.9) can provide the current latitude andlongitude to Mobile Device (19.2). Alternatively, Geo Services (19.9)can provide a marker which serves as an indicator to assist MobileDevice (19.2) determine its current location. For example, if MobileDevice (19.2) receives a marker from Geo Services (19.9), Mobile Devicecan compare the marker to a list of stored markers on Mobile Device(19.2) to determine the current location. Alternatively, if MobileDevice (19.2) cannot use a previously stored location marker todetermine the current location, Mobile Device (19.2) may request alocation ID from the Secure Payment Computing Device (19.4). Locationmarker may also be obtained from Location Beacon (19.10). Secure PaymentComputing Device (19.4) is operable to perform numerous functions inconnection with the validation of a payment transaction (or non-paymenttransactions as further defined in FIGS. 69 and 70), functions includingbut not limited to: decoding dynamic mobile PAN numbers, identifyingmobile device numbers using mobile PAN numbers, account numbers ordevice tokens, validating mobile PIN numbers, selecting card numbers andalternate PIN numbers based on settings profile and velocity, generatingmobile approval codes, and performing other related steps as required bythe Settings (19.4.1). Secure Payment Computing Device (19.4) iscomprised of a Host Mobile PAN Module (19.4.5) which is operable togenerate a static mobile PAN number (19.9.2), static mobile PAN numberstored on mobile device (19.2). Alternatively, host mobile PAN module isoperable to decode a dynamic mobile PAN number received from mobiledevice (19.2) using defined algorithms (see FIG. 72). Secure PaymentComputing Device (19.4) can communicate to Payment Networks andAlternate Networks (19.5) using the Alternate Secure Payment NetworkCommunication Link (19.7.4). Secure Payment Computing Device (19.4) cancommunicate to Payment Acquirer or Alternate Acquirer (19.6) using theSecure Payment Network Communication Link (19.7.8). POS device (19.1)can communicate to Payment Acquirer or Alternate Acquirer (19.6) usingAcquirer Network Communication Link (19.7.6). Payment Acquirer orAlternate Acquirer (19.6) can communicate with Payment Networks andAlternate Networks (19.5) using Payment Network Communication Link(19.7.5). Payment Networks and Alternate Networks (19.5) can communicatewith Issuers (19.8) using Issuer Network Communication Link (19.7.7).Components may also include registered wearable devices (19.11) such aseye glasses, watches, rings and other devices operable to receivebiometric inputs and communicate biometric data to other devices andcomponents. For example, Link (19.11.1) shows wearable devicescommunicating with POS device (19.1) and Link (19.11.2) shows wearabledevices communicating with Mobile device (19.2). Wearable devices mayalso be operable to receive BLE signal from Beacon (19.10). Aspreviously described in FIG. 4, elements of a Mobile Wallet System maybe located on the mobile device as depicted in (19.2.3) or on the remoteserver which is accessed by the mobile device. As such the Mobile WalletSystem may be physically co-located within the Secure Payment ComputingDevice as depicted in (19.4.6) or it may be co-located at the Acquirer(21.6) or at a facility operated by the Mobile Network Operator (e.g.AT&T, Verizon, Sprint, etc.).

FIG. 20 illustrates an architecture and components for enhanced ATMsecurity comprised of ATM device (20.1), which is further comprised ofTerminal ID (20.1.1) and Merchant ID (20.1.2); ATM device (20.1) incommunication with Mobile Device (20.2) using Local Communication Link(20.7.1). Local Communication Link (20.7.1) may be based on an NFCcommunication protocol such as ISO 14443, Mifare or other NFC protocols.Alternatively, Local Communication Link may be based on low energy bluetooth (BLE), RFID or other protocols or optical scanning of a code suchas a QR code. Mobile Device (20.2) is further comprised of Mobile PANModule (20.2.1) and Mobile PAN (20.2.2). Mobile PAN Module (20.2.2) isfunctional to receive and store a static mobile PAN number onto MobileDevice (20.2), the static mobile PAN received from Secure PaymentComputing Device (20.4). Alternatively, Mobile PAN Module (20.2.1) isalso functional to generate a dynamic mobile PAN based mobile PANrequirements derived from Settings (20.4.1) and using defined algorithms(see FIG. 72). Mobile Device (20.2) may be further comprised of SecureElement (20.2.4). Mobile Device (20.2) is in communication with SecurePayment Computing Device (20.4) using Mobile Communication Link(20.7.2), Network (20.3) and Host Communication Link (20.7.3). Network(20.3) may be comprised of a mobile communication network such as amobile network provided by at&t or Verizon. Alternatively, Network(20.3) may be comprised of a local area network. In either case, Network(20.3) facilitates the communication between Mobile Device (20.2) andSecure Payment Computing Device (20.4). Geo Services (20.9) arefunctional to provide current location information to Mobile Device(20.2). Geo Services (20.9) can provide the current latitude andlongitude to Mobile Device (20.2). Alternatively, Geo Services (20.9)can provide a marker which serves as an indicator to assist MobileDevice (20.2) determine its current location. For example, if MobileDevice (20.2) receives a marker from Geo Services (20.9), Mobile Devicecan compare the marker to a list of stored markers on Mobile Device(20.2) to determine the current location. Alternatively, if MobileDevice (20.2) cannot use a previously stored location marker todetermine the current location, Mobile Device (20.2) may request alocation ID from the Secure Payment Computing Device (20.4). Locationmarker may also be obtained from Location Beacon (20.10). Secure PaymentComputing Device (20.4) is operable to perform numerous functions inconnection with the validation of payment and non-payment transactions,functions including but not limited to: decoding dynamic mobile PANnumbers, identifying mobile device numbers using mobile PAN numbers,Device Tokens, and Account Numbers, validating mobile PIN numbers,selecting card numbers and alternate PIN numbers based on settingsprofile and velocity, generating mobile approval codes, and performingother related steps as required by the Settings (20.4.1). Secure PaymentComputing Device (20.4) is comprised of a Host Mobile PAN Module(20.4.5) which is operable to generate a static mobile PAN number(20.9.2), static mobile PAN number stored on mobile device (20.2).Alternatively, host mobile PAN module is operable to decode a dynamicmobile PAN number received from mobile device (20.2) using definedalgorithms (FIG. 72). Secure Payment Computing Device (20.4) cancommunicate to Payment Networks and Alternate Networks (20.5) using theAlternate Secure Payment Network Communication Link (20.7.4). SecurePayment Computing Device (20.4) can communicate to Payment Acquirer orAlternate Acquirer (20.6) using the Secure Payment Network CommunicationLink (20.7.8). ATM device (20.1) can communicate to Bank or Merchant(Alternate) Acquirer (20.6) using Acquirer Network Communication Link(20.7.6). [Note—While most ATMs are operated by Banks, Merchants mayallow ATMs to be placed in their stores by Independent SalesOrganizations (ISOs) acting as agents for alternate acquirers.Transactions may be first acquired by the merchant or an alternateacquirer before ultimately being routed to the Issuer for approval].Payment Acquirer or Alternate Acquirer (20.6) can communicate withPayment Networks and Alternate Networks (20.5) using Payment NetworkCommunication Link (20.7.5). Payment Networks and Alternate Networks(20.5) can communicate with Issuers (20.8) using Issuer NetworkCommunication Link (20.7.7). Components may also include registeredwearable devices (20.11) such as eye glasses, watches, rings and otherdevices operable to receive biometric inputs and communicate biometricdata to other devices and components. For example, Link (20.11.1) showswearable devices communicating with POS device (20.1) and Link (20.11.2)shows wearable devices communicating with Mobile device (20.2). Wearabledevices may also be operable to receive BLE signal from Beacon (20.10).As previously described in FIG. 4, elements of a Mobile Wallet Systemmay be located on the mobile device as depicted in (20.2.3) or on theremote server which is accessed by the mobile device. As such the MobileWallet System may be physically co-located within the Secure PaymentComputing Device as depicted in (20.4.6) or it may be co-located at theAcquirer (21.6) or at a facility operated by the Mobile Network Operator(e.g. AT&T, Verizon, Sprint, etc.).

FIG. 21 illustrates an architecture and components for enhancedeCommerce security comprised of Mobile Device (21.2) using RemoteCommunication Link (21.7.1) in communication with eCommerce Site(21.11). eCommerce Site (21.11) which is further comprised of one ormore of Terminal ID (21.11.1) and Merchant ID (21.11.2). RemoteCommunication Link (21.7.1) consisting of HTTPs or similar secureencrypted protocol suitable for eCommerce purposes. Mobile Device (21.2)is further comprised of Mobile PAN Module (21.2.1) and Mobile PAN(21.2.2). Mobile PAN Module (21.2.2) is functional to receive and storea static mobile PAN number onto Mobile Device (21.2), static mobile PANreceived from Secure Payment Computing Device (21.4). Alternatively,Mobile PAN Module (21.2.1) is also functional to generate a dynamicmobile PAN based mobile PAN requirements derived from Settings (21.4.1)and using defined algorithms (see FIG. 72). Mobile Device (21.2) may befurther comprised of Secure Element (21.2.4). Mobile Device (21.2) is incommunication with Secure Payment Computing Device (21.4) using MobileCommunication Link (21.7.2), Network (21.3) and Host Communication Link(21.7.3). Network (21.3) may be comprised of a mobile communicationnetwork such as a mobile network provided by at&t or Verizon.Alternatively, Network (21.3) may be comprised of a local area network.In either case, Network (21.3) facilitates the communication betweenMobile Device (21.2) and Secure Payment Computing Device (21.4). GeoServices (21.9) are functional to provide current location informationto Mobile Device (21.2). Geo Services (21.9) can provide the currentlatitude and longitude to Mobile Device (21.2). Alternatively, GeoServices (21.9) can provide a marker which serves as an indicator toassist Mobile Device (21.2) determine its current location. For example,if Mobile Device (21.2) receives a marker from Geo Services (21.9),Mobile Device can compare the marker to a list of stored markers onMobile Device (21.2) to determine the current location. Mobile Devicemay be configured to securely store locations that are pre-approved ornon-approved by the consumer or Issuing Bank. Locations may beperiodically updated by the SPCD. Alternatively, if Mobile Device (21.2)cannot use a previously stored location marker to determine or approvethe current location, Mobile Device (21.2) may request a location IDfrom the Secure Payment Computing Device (21.4). Location marker mayalso be obtained from Location Beacon (21.10). Secure Payment ComputingDevice (21.4) is operable to perform numerous functions in connectionwith the validation of payment and non-payment transactions, functionsincluding but not limited to: decoding dynamic mobile PAN numbers,identifying mobile device numbers using mobile PAN numbers, DeviceTokens, or Account numbers, validating mobile PIN numbers, selectingcard numbers and alternate PIN numbers based on settings profile andvelocity, generating mobile approval codes, and performing other relatedsteps as required by the Settings (21.4.1). Secure Payment ComputingDevice (21.4) is comprised of a Host Mobile PAN Module (21.4.5) which isoperable to generate a static mobile PAN number (21.9.2), static mobilePAN number stored on mobile device (21.2). Alternatively, host mobilePAN module is operable to decode a dynamic mobile PAN number receivedfrom mobile device (21.2) using defined algorithms (FIG. 72). SecurePayment Computing Device (21.4) can communicate to Payment Networks andAlternate Networks (21.5) using the Alternate Secure Payment NetworkCommunication Link (21.7.4). Secure Payment Computing Device (21.4) cancommunicate to Payment Acquirer or Alternate Acquirer (21.6) using theSecure Payment Network Communication Link (21.7.8). eCommerce Site(21.11) can communicate to Payment Acquirer or Alternate Acquirer (21.6)using Acquirer Network Communication Link (21.7.6). Payment Acquirer orAlternate Acquirer (21.6) can communicate with Payment Networks andAlternate Networks (21.5) using Payment Network Communication Link(21.7.5). Payment Networks and Alternate Networks (21.5) can communicatewith Issuers (21.8) using Issuer Network Communication Link (21.7.7).Components may also include registered wearable devices (21.11) such aseye glasses, watches, rings and other devices operable to receivebiometric inputs and communicate biometric data to other devices andcomponents. For example Link (21.11.1) shows wearable devicescommunicating with POS device (21.1) and Link (21.11.2) shows wearabledevices communicating with Mobile device (21.2). Wearable devices mayalso be operable to receive BLE signal from Beacon (21.10). Aspreviously described in FIG. 4, elements of a Mobile Wallet System maybe located on the mobile device as depicted in (21.2.3) or on the remoteserver which is accessed by the mobile device. As such the Mobile WalletSystem may physically co-located within the Secure Payment ComputingDevice as depicted in (21.4.6) or it may be co-located at the Acquirer(21.6) or at a facility operated by the Mobile Network Operator (e.g.AT&T, Verizon, Sprint, etc.).

FIG. 22 illustrates a standard POS payment flow using a mobile PAN. Forexample, a Consumer (22.1) may initiate a payment transaction depictedusing action line (22.01), which causes Mobile Device (22.2) to read astatic Mobile PAN number or generate a dynamic Mobile PAN number. IfMobile Device (22.2) is configured with a static Mobile PAN number, Step(22.02) will read the previously stored static Mobile PAN.Alternatively, if Mobile Device (22.2) is configured to generate adynamic Mobile PAN, Step (22.02) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Actionline (22.03) depicts the provisioning of the Mobile PAN number fromMobile Device (22.2) to POS (22.3). The provisioning of the Mobile PANnumber can be completed using one of a manual, NFC, BLE, RFID, QR Codeor other suitable communication protocol. POS (22.3) accepts the MobilePAN number provisioned from Mobile Device (22.2) using Step (22.04). POSdevice (22.3), having already calculated the total tender amount due(22.3.1), transmits the Mobile PAN number and tender amount due toAcquirer (22.4) as depicted by action line (22.05). Acquirer (22.4)using Step (22.06) evaluates the Mobile PAN number from POS (22.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Acquirer (22.4) transmits the Mobile PAN andtender amount to the SPCD (22.6) as depicted in action line (22.07).Using Step (22.08), SPCD (22.06) uses the Mobile PAN number to identifythe Mobile Device (see FIG. 56). If required the SPCD (22.6) can decodea dynamic Mobile PAN number using the Host Mobile PAN Module (19.4.5) aspreviously described in FIG. 19. Having now identified the MobileDevice, SPCD (22.6) initiates a mobile authentication message to MobileDevice (22.2) as depicted in action line (22.09); mobile approvalmessage comprised of at least the tender amount and can include otherinformation available in the Settings and Database Tables (22.7).Consumer (22.1) can approve the payment transaction using Mobile Device(22.2); approval can be in the form of a Mobile PIN, biometric, or otherfactors or combinations of factors as available in and prescribed bySettings and Database Tables (22.7). Action Line (22.11) depicts theMobile Authentication Message sent from Mobile Device (22.2) to SPCD(22.6); the message comprised of one or more of a mobile PIN, tokens,and biometric factors. Tokens may be associated with the Mobile Deviceand used by the SPCD to validate the device. Tokens may also beassociated with the Mobile PAN number to prevent fraudulent use of theMobile PAN. Tokens may also be sent in lieu of sending biometric factorswhich may be validated locally on the mobile device. SPCD (22.6)validates the Mobile Approval Message in Step (22.13); validationcompleted using data received in Action Line (22.12), data comprised ofone or more of a Mobile PIN, tokens, biometrics, or other factors suchas the velocity of payment transactions submitted using this Mobile PANand/or device. Other more comprehensive authentication rules may beapplied to the transaction as required. For example, if user's defaultPIN is registered in the User PIN Table (FIG. 51), this default PIN maybe used to authenticate the payment. However, if the user's device hasbeen registered in the Device, Device PIN, Token Table (FIG. 50), thenthis PIN would be used for authentication in preference to the defaultPIN from the User PIN Table. Having approved the payment transaction forfurther processing, the SPCD (22.6) formats the Payment ApprovalTransaction by inserting a registered payment card number (e.g. IssuerPAN) or payment account unique identifier (such as PayPal Accountregistered email address or Bitcoin account no.) and forwards PaymentApproval Transaction to Acquirer (22.4) using Action Line (22.14). Ifthe registered payment card number is one of a PIN Debit Account,payment approval data may be further formatted to include one of analternate PIN, partial PIN, Issuer PIN, or other approved PIN Debitfield (such as a null value, sequence number, or static value) asavailable in and prescribed by the Settings and Database Tables (22.7).The Acquirer (22.4) receives the Payment Transaction data contained inthe Payment Approval Transaction and sends Payment Transaction to theappropriate Payment Network (22.5); Payment Transaction comprised of onemore of an Issuer PAN, Tender Amount, and PIN Debit field (if required).Payment Network (22.15) obtains approval from the Payment Account Issuerusing Step (22.16); Payment Account Issuer may be one of an issuing bankor alternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (22.5) sendsIssuer Approval Message to Payment Acquirer (22.4) using Action Line(22.17). Acquirer (22.4) forwards the Issuer Approval Message to the POS(22.3) using Action Line (22.19) and also forwards the Issuer ApprovalMessage to the SPCD (22.6) using Action Line (22.18). The process iscompleted when SPCD (22.6) forwards a notification of Issuer Approval tothe Mobile Device (22.2) using Action Line (22.20). Referring now toFIG. 19 in conjunction with FIG. 22, Action Line (22.03) correlates toLocal Communication Link (19.7.1); Action Line (22.05) correlates toAcquirer Network Communication Link (19.7.6); Action Line (22.07)correlates to Secure Payment Network Communication Link (19.7.8); ActionLine (22.09) correlates to Host Communication Link (19.7.3) incommunication with Mobile/Local Network (19.3) in communication withMobile Communication Link (19.7.2); Action Line (22.15) correlates toPayment Network Communication Link (19.7.5); and Action (22.16) usesIssuer Network Communication Link (19.7.7) although the Issuer is notshown in FIG. 22.

FIG. 23 illustrates an alternate standard POS payment flow using amobile PAN.

The primary difference between FIG. 22 and FIG. 23 is the point in theflow where the Mobile Authentication is executed. For example, aConsumer (23.1) may initiate a payment transaction depicted using actionline (23.01), which causes Mobile Device (23.2) to read a static MobilePAN number or generate a dynamic Mobile PAN number. If Mobile Device(23.2) is configured with a static Mobile PAN number, Step (23.02) willread the previously stored Mobile PAN. Alternatively, if Mobile Device(23.2) is configured to generate a dynamic Mobile PAN, Step (23.02) willgenerate a dynamic Mobile PAN number using a random value and definedalgorithms (FIG. 72). Action line (23.03) depicts the provisioning ofthe Mobile PAN number from Mobile Device (23.2) to POS (23.3). Theprovisioning of the Mobile PAN number can be completed using one of amanual, NFC, BLE, RFID, QR code or other suitable communicationprotocol. POS (23.3) accepts the Mobile PAN number provisioned fromMobile Device (23.2) using Step (23.04). POS device (23.3), havingalready calculated the total tender amount due (23.3.1), transmits theMobile PAN number and tender amount due to Acquirer (23.4) as depictedby action line (23.05). Acquirer forwards Payment Transaction includingMobile PAN and tender amount to Payment Network (23.5) using Action Line(23.06) Payment Network (23.5) using Step (23.07) evaluates the MobilePAN number from POS (23.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Payment Network (23.5)transmits the Mobile PAN and tender amount to the SPCD (23.6) asdepicted in action line (23.08). Using Step (23.09), SPCD (23.06) usesthe Mobile PAN number to identify the Mobile Device (see FIG. 56). Ifrequired the SPCD (23.6) can decode a dynamic Mobile PAN number usingthe Host Mobile PAN Module (19.4.5) as previously described in FIG. 19.Having now identified the Mobile Device, SPCD (23.6) initiates a mobileauthentication message to Mobile Device (23.2) as depicted in actionline (23.10); Mobile Approval Message comprised of at least the tenderamount and can include other information available in or required by theSettings and Database Tables (23.7). Consumer (23.1) can approve thepayment transaction using Mobile Device (23.2); approval can be in theform of a Mobile PIN, biometric, or other factors or combinations offactors as prescribed by and available in the Settings and DatabaseTables (23.7). Action Line (23.12) depicts the Mobile AuthenticationMessage sent from Mobile Device (23.2) to SPCD (23.6); message comprisedof one or more of a mobile PIN, tokens, and biometric factors. Tokensmay be associated with the Mobile Device and used by the SPCD tovalidate the device. Tokens may also be associated with the Mobile PANnumber to prevent fraudulent use of the Mobile PAN. Tokens may also besent in lieu of sending biometric factors which may be validated locallyon the mobile device. SPCD (23.6) validates the Mobile Approval Messagein Step (23.13); validation completed using data received in Action Line(23.13), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors such as the velocity of paymenttransactions submitted using this Mobile PAN and/or device. Other morecomprehensive authentication rules may be applied to the transaction asrequired. For example, if the user has registered the Mobile PAN to beused with a specific Mobile Device as reflected in the Mobile PAN,Device, Mobile PIN Table (FIG. 56), the Mobile PIN registered in thistable should be used and a token associated with the Mobile PAN would berequired to be present in the authentication message (23.12). Havingapproved the payment transaction for further processing, the SPCD (23.6)formats the Payment Approval Transaction by inserting a registeredpayment card number (e.g. Issuer PAN) or payment account uniqueidentifier (such as PayPal Account registered email address or Bitcoinaccount no) and forwards Payment Approval Transaction to Payment Network(23.5) using Action Line (23.15). If the registered payment card numberis one of a PIN Debit Account, payment approval data may be furtherformatted to include one of an alternate PIN, partial PIN, Issuer PIN,or other approved PIN Debit field (such as a null value, sequencenumber, or static value) as prescribed by and available in the Settingsand Database Tables (23.7) The Payment Network (23.5) receives thePayment Transaction data contained in the Payment Approval Transactionand Payment Network (23.16) obtains approval from the Payment AccountIssuer using Step (23.16); Payment Account Issuer may be one of anissuing bank or alternative payment issuer such as PayPal or Bitcoin.After receiving approval from the Payment Account Issuer, PaymentNetwork (23.5) sends Issuer Approval Message to Payment Acquirer (23.4)using Action Line (23.17). Acquirer (23.4) forwards the Issuer ApprovalMessage to the POS (23.3) using Action Line (23.19) and also forwardsthe Issuer Approval Message to the SPCD (23.6) using Action Line(23.18). The process is completed when SPCD (23.6) forwards anotification of Issuer Approval to the Mobile Device (23.2) using ActionLine (23.20). Referring now to FIG. 19 in conjunction with FIG. 23,Action Line (23.03) correlates to Local Communication Link (19.7.1);Action Line (23.05) correlates to Acquirer Network Communication Link(19.7.6); Action Line (23.08) correlates to Alternate Secure PaymentNetwork Communication Link (19.7.4); Action Line (23.10) correlates toHost Communication Link (19.7.3) in communication with Mobile/LocalNetwork (19.3) in communication with Mobile Communication Link (19.7.2);Action Line (23.17) correlates to Payment Network Communication Link(19.7.5); and Action (23.16) uses Issuer Network Communication Link(19.7.7) although the Issuer is not shown in FIG. 23.

FIG. 24 illustrates an enhanced POS payment flow using a mobile PAN. Forexample, a Consumer (24.1) may initiate a payment transaction depictedusing action line (24.01), which causes Mobile Device (24.2) using Step(24.02) to get one or more of the current location, Merchant ID (MID),and Terminal ID (TID); location obtained from Geo Location Services(19.9) or using local beacon (19.10); MID and TID obtained from the POS(24.3) using one of RFID, BLE or other similar method and transferred toMobile Device (24.2). MID and TID may also be obtained by scanning astatic or dynamic code such as a QR code. Now using Step (24.04), MobileDevice (24.2) reads a static Mobile PAN or generates a dynamic MobilePAN number. If Mobile Device (24.2) is configured with a static MobilePAN number, Step (24.04) will read the previously stored Mobile PAN.Alternatively, if Mobile Device (24.2) is configured to generate adynamic Mobile PAN, Step (24.04) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Next,using Action Line (24.05), Mobile Device (24.02) transmits Mobile PAN,MID, TID, and Location to SPCD (24.6). SPCD (24.06) is operable to usethe Mobile PAN number to identify the Mobile Device (see FIG. 56). Ifrequired the SPCD (24.6) can decode a dynamic Mobile PAN number usingthe Host Mobile PAN Module (19.4.5) as previously described in FIG. 19.Having now identified the Mobile Device, using Step (24.07) SPCD (24.6)reads Settings and Database Tables (24.7) to obtain a list of approvedand disapproved Locations, MIDs and TIDs associated with the registeredMobile PAN (see FIG. 46, Registered Card or Account Location Table) andusing Step (24.09) validates that the Mobile PAN may be used at thecombination of one or more of Location, MID, and TID. The Location, MID,and TID may also be validated locally by the Mobile Device using dataperiodically downloaded and securely stored on the Mobile Device. Thismethod can be useful where network signals are weak. Having nowvalidated the Location, MID, and TID in accordance with requirements,SPCD (24.6) initiates a valid MID, TID, Location message and transmitsmessage using Action Line (24.10). Consumer (24.1) is notified by MobileDevice (24.2) that the Location, TID, and MID are approved and usingStep (24.12) initiates the Mobile Payment sequence. It should be notedthat the Mobile Device may be pre-configured to perform Step (24.12)thereby eliminating the need for the Consumer to initiate the MobilePayment sequence. Action line (24.13) depicts the provisioning of theMobile PAN number from Mobile Device (24.2) to POS (24.3). Theprovisioning of the Mobile PAN number can be completed using one of amanual, NFC, BLE, RFID, QR Code or other suitable communicationprotocol. POS (24.3) accepts the Mobile PAN number provisioned fromMobile Device (24.2) using Step (24.14). POS device (24.3), havingalready calculated the total tender amount due (24.3.1), transmits theMobile PAN number and tender amount due to Acquirer (24.4) as depictedby action line (24.15). Acquirer (24.4) using Step (24.16) evaluates theMobile PAN number from POS (24.2) to determine if a MobileAuthentication is required. If a Mobile Authentication is required,Acquirer (24.4) transmits the Mobile PAN and tender amount to the SPCD(24.6) as depicted in action line (24.17). Using Step (24.08), SPCDhaving previously identified the Mobile Device, initiates a mobileauthentication message to Mobile Device (24.2) as depicted in actionline (24.18); mobile approval message comprised of at least the tenderamount and can include other information available in and prescribed bythe Settings and Database Tables (24.7) such as the merchant orlocation. Consumer (24.1) can approve the payment transaction usingMobile Device (24.2); approval can be in the form of a Mobile PIN,biometric, or other factors or combinations of factors as available inand prescribed by the Settings and Database Tables (24.7). Action Line(24.20) depicts the Mobile Authentication Message sent from MobileDevice (24.2) to SPCD (24.6); message comprised of one or more of amobile PIN, tokens, and biometric factors. Tokens may be associated withthe Mobile Device and used by the SPCD to validate the device. Tokensmay also be associated with the Mobile PAN number to prevent fraudulentuse of the Mobile PAN. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (24.6) validates the Mobile Approval Message in Step (24.22);validation completed using data received in Action Line (24.21), datacomprised of one or more of a Mobile PIN, tokens, biometrics, and/orother required factors for authenticating payment transactions submittedusing this Mobile PAN. Other more comprehensive rules may be applied tothe transaction as required. For example, if the Mobile PAN isregistered in the Entity Approval Criteria Table (FIG. 58), the purchaseamount may be subject to a per transaction maximum at a specificlocation. It should be noted that the Mobile Approval Message depictedin Action Line (24.20) may be combined with Location Approval Message(24.05) and that the Initiate Pay Sequence (24.12) may be combined withInitiate Payment (24.01) thereby eliminating the need for the Consumerto separately initiate the pay sequence (24.12). Having approved thepayment transaction for further processing, the SPCD (24.6) formats thePayment Approval Transaction by inserting a registered payment cardnumber (e.g. Issuer PAN) or payment account unique identifier (such asPayPal Account registered email address or Bitcoin account no) andforwards Payment Approval Transaction to Acquirer (24.4) using ActionLine (24.23). If the registered payment card number is one of a PINDebit Account, payment approval data may be further formatted to includeone of an alternate PIN, partial PIN, Issuer PIN, or other approved PINDebit field (such as a null value, sequence number, or static value) asprescribed by and available in the Settings and Database Tables (24.7).The Acquirer (24.4) receives the Payment Transaction data contained inthe Payment Approval Transaction and sends Payment Transaction to theappropriate Payment Network (24.5); Payment Transaction comprised of onemore of an Issuer PAN, Tender Amount, and PIN Debit Field (if required).Payment Network (24.5) obtains approval from the Payment Account Issuerusing Step (24.25); Payment Account Issuer may be one of an issuing bankor alternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (24.5) sendsIssuer Approval Message to Payment Acquirer (24.4) using Action Line(24.26). Acquirer (24.4) forwards the Issuer Approval Message to the POS(24.3) using Action Line (24.19) and also forwards the Issuer ApprovalMessage to the SPCD (24.6) using Action Line (24.27). The process iscompleted when SPCD (24.6) forwards a notification of Issuer Approval tothe Mobile Device (24.2) using Action Line (24.29).

FIG. 24R illustrates a reverse POS payment flow using a mobile PAN. Forexample, a Consumer (24R.1) may initiate a payment transaction depictedusing action line (24R.01), which causes Mobile Device (24R.2) to read astatic Mobile PAN number or generate a dynamic Mobile PAN. If MobileDevice (24R.2) is configured with a static Mobile PAN number, Step(24R.02) will read the previously stored static Mobile PAN.Alternatively, if Mobile Device (24R.2) is configured to generate adynamic Mobile PAN, Step (24R.02) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Actionline (24R.03) depicts the provisioning of the Mobile PAN number fromMobile Device (24R.2) to POS (24R.3). The provisioning of the Mobile PANnumber can be completed using one of a manual, NFC, BLE, RFID, QR Codeor other suitable communication protocol. POS (24R.3) accepts the MobilePAN number provisioned from Mobile Device (24R.2) using Step (24R.04).POS (24R.3), having already calculated the total tender amount due(24R.3.1), transmits the Mobile PAN number and tender amount due toAcquirer (24R.4) as depicted by action line (24R.05). Acquirer (24R.4)using Step (24R.06) evaluates the Mobile PAN number from POS (24R.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Acquirer (24R.4) transmits the Mobile PANand tender amount to the SPCD (24R.6) as depicted in action line(24R.07). Using Step (24R.08), SPCD (24R.06) uses the Mobile PAN numberto identify the Mobile Device (see FIG. 56). If required the SPCD(24R.6) can decode a dynamic Mobile PAN number using the Host Mobile PANModule (19.4.5) as previously described in FIG. 19. Having nowidentified the Mobile Device, using Step (24R.08) SPCD (32.6) readsSettings and Database Tables (24R.7) using step (24R.09) to obtain alist of approved and disapproved Locations and other authenticationrequirements for Mobile PAN. Having now identified the authenticationrequirements (step 24R.10) for this Mobile PAN, SPCD (24R.6) initiates amobile authentication message to Mobile Device (24R.2) as depicted inaction line (24R.12); mobile approval message comprised of at least thetender amount and can include other information available in theSettings and Database Tables (24R.7). Consumer (24R.1) can approve thepayment transaction using Mobile Device (24R.2); approval can be in theform of a Mobile PIN, biometric, or other factors or combinations offactors (such as Mobile PAN Token and Device Token) as available in andprescribed by Settings and Database Tables (24R.7). Action Line (24R.13)depicts the entry of the required authentication elements (such as PINor biometric factors) by Consumer (24R.1). In step 32R.14, Mobile Devicedetermines its current location; location obtained from Geo LocationServices (19.9) or local beacon (19.10). Having now obtained therequired authentication elements and the current location, the MobileAuthentication Message is sent from Mobile Device (24R.2) to SPCD(24R.6) as shown in Action Line (24R.15); message comprised of one ormore of a mobile PIN, tokens, and biometric and location indicatorcomprised of one of a registered Location ID or equivalent latitude andlongitude. SPCD (24R.6) validates the Mobile Approval Message in Step(24R.17); validation completed using data received in Action Line(24R.16), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors such as the velocity of paymenttransactions submitted using this Mobile PAN and/or device. Other morecomprehensive authentication rules may be applied to the transaction asrequired. For example, if the Mobile PAN is registered in the DynamicPIN Card Selection Table (FIG. 60), the system will select the defaultpayment card based on the PIN entered to authenticate the transaction.Having approved the payment transaction for further processing, the SPCD(24R.6) formats the Payment Approval Transaction by inserting aregistered payment card number (e.g. Issuer PAN) or payment accountunique identifier (such as PayPal Account registered email address orBitcoin account no) and forwards Payment Approval Transaction to PaymentNetwork (24R.5) using Action Line (24R.18). If the registered paymentcard number is one of a PIN Debit Account, payment approval data may befurther formatted to include one of an alternate PIN, partial PIN,Issuer PIN, or other approved PIN Debit field (such as a null value,sequence number, or static value) as available in and prescribed by theSettings and Database Tables (24R.7). The Payment Network (24R.5)receives the Payment Transaction data contained in the Payment ApprovalTransaction and obtains approval from the Payment Account Issuer usingStep (24R.19); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (24R.5) sendsIssuer Approval Message to SPCD (24R.6) using Action Line (24R.20). SPCD(24R.6) generates a mobile approval code (step 32R.21) and forwards theIssuer Approval Message with mobile approval code to the Acquirer(24R.4) using Action Line (24R.22) and also forwards the Issuer ApprovalMessage with mobile approval code to the Mobile Device (24R.2) usingAction Line (24R.23). Consumer (24R.1) either enters the mobile approvalcode into the POS (24R.2) shown in Action Line (24R.24) or mobileapproval code is transmitted to POS device using one of NFC, RFID, BLE,or QR code. POS (24R.3) forwards mobile approval code to Acquirer(24R.4) as shown in Action Line (24R.25). In Step (24R.26) the Acquirer(24R.5) validates the mobile approval code by comparing the mobileapproval code received from the SPCD (24R.6) to the mobile approval codereceived from the POS (24R.3) The process is completed when Acquirer(24R.5) forwards a notification of Issuer Approval to the POS (24R.3)using Action Line (24R.27).

FIG. 25 illustrates an alternate enhanced POS payment flow using amobile PAN.

For example, a Consumer (25.1) may initiate a payment transactiondepicted using action line (25.01), which causes Mobile Device (25.2)using Step (25.02) to get one or more of the current location, MerchantID (MID), and Terminal ID (TID); location obtained from Geo LocationServices (19.9) or local beacon (19.10); MID and TID obtained from thePOS (25.3) using one of RFID, BLE, QR Code or other similar method andtransferred to Mobile Device (25.2). The Mobile Device may be operableto immediately approve or reject a transaction based on data previouslydownloaded and securely stored onto the secure element of the MobileDevice. Now using Step (25.04), Mobile Device (25.2) reads or generatesa Mobile PAN number. If Mobile Device (25.2) is configured with a staticMobile PAN number, Step (25.04) will read the previously stored MobilePAN. Alternatively, if Mobile Device (25.2) is configured to generate adynamic Mobile PAN, Step (25.04) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Next, ifthe location or merchant has not already been rejected offline usinglocal data, using Action Line (25.05), Mobile Device (25.02) transmitsMobile PAN, MID, TID, and Location to SPCD (25.6). SPCD (25.06) isoperable to use the Mobile PAN number to identify the Mobile Device (seeFIG. 56). If required the SPCD (25.6) can decode a dynamic Mobile PANnumber using the Host Mobile PAN Module (19.4.5) as previously describedin FIG. 19. Having now identified the Mobile Device, using Step (25.07)SPCD (25.6) reads Settings and Database Tables (25.7) to obtain a listof approved and disapproved Locations, MIDs and TIDs associated with theregistered Mobile PAN and using Step (25.09) validates that the MobilePAN may be used at the combination of one or more of Location, MID, andTID; combination requirements determined by the Settings Tables andactual combinations determined by the Database Tables. For example afirst Issuing Bank may prohibit use of accounts at specific locationswhile a second Issuing Bank may allow the same locations to be used.Having now validated the Location, MID, and TID in accordance withrequirements, SPCD (25.6) initiates a valid MID, TID, Location messageand transmits message using Action Line (25.10). Consumer (25.1) isnotified by Mobile Device (25.2) that the Location, TID, and MID areapproved and using Step (25.12) initiates the Mobile Payment sequence.It should be noted that the Mobile Device may be pre-configured toautomatically perform Step (25.12) thereby eliminating the need for theConsumer to initiate the Mobile Payment sequence. Action line (25.13)depicts the provisioning of the Mobile PAN number from Mobile Device(25.2) to POS (25.3). The provisioning of the Mobile PAN number can becompleted using one of a manual, NFC, BLE, RFID, QR Code or othersuitable communication protocol. POS (25.3) accepts the Mobile PANnumber provisioned from Mobile Device (25.2) using Step (25.14). POSdevice (25.3), having already calculated the total tender amount due(25.3.1), transmits the Mobile PAN number and tender amount due toAcquirer (25.4) and as depicted by action line (25.15) Acquirer routestransaction to Payment Network (25.5). Payment Network (25.5) using Step(25.16) evaluates the Mobile PAN number from POS (25.2) to determine ifa Mobile Authentication is required. If a Mobile Authentication isrequired, Acquirer (25.5) transmits the Mobile PAN and tender amount tothe SPCD (25.6) as depicted in action line (25.17). Using Step (25.08),SPCD having previously identified the Mobile Device, initiates a mobileauthentication message to Mobile Device (25.2) as depicted in actionline (25.18); mobile approval message is comprised of at least thetender amount and can include other information available in andprescribed by the Settings and Database Tables (25.7). Consumer (25.1)can approve the payment transaction using Mobile Device (25.2); approvalcan be in the form of a Mobile PIN, biometric, or other factors orcombinations of factors as prescribed by the Settings Tables) and basedon information stored in the Database Tables (19.4.2). Action Line(25.20) depicts the Mobile Authentication Message sent from MobileDevice (25.2) to SPCD (25.6); message comprised of one or more of amobile PIN, tokens, and biometric factors. Tokens may be associated withthe Mobile Device and used by the SPCD to validate the device. Tokensmay also be associated with the Mobile PAN number to prevent fraudulentuse of the Mobile PAN. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (25.6) validates the Mobile Approval Message in Step (25.22);validation completed using data received in Action Line (25.21), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions submitted usingthis Mobile PAN and/or device. It should be noted that the MobileApproval Message depicted in Action Line (25.20) may be combined withLocation Approval Message (25.05) and that the Initiate Pay Sequence(25.12) may be combined with Initiate Payment (25.01) therebyeliminating the need for the Consumer to separately initiate the paysequence (25.12). Other more comprehensive authentication rules may beapplied to the transaction as required. For example, if the Mobile PANis registered in the Venue, Biometric Table (FIG. 61), a bodytemperature reading may be required for a payment in excess of aspecific amount at a POS location. Having approved the paymenttransaction for further processing, the SPCD (25.6) formats the PaymentApproval Transaction by inserting a registered payment card number (e.g.Issuer PAN) or payment account unique identifier (such as PayPal Accountregistered email address or Bitcoin account no) and forwards PaymentApproval Transaction to Acquirer (25.4) using Action Line (25.23). Ifthe registered payment card number is one of a PIN Debit Account,payment approval data may be further formatted to include one of analternate PIN, partial PIN, Issuer PIN, or other approved PIN Debitfield (such as a null value, sequence number, or static value) asprescribed by and available in the Settings and Data Base Tables (25.7).The Payment Network (25.5) receives the Payment Transaction datacontained in the Payment Approval Transaction and sends PaymentTransaction to the appropriate Issuer for approval; Payment Transactioncomprised of one more of an Issuer PAN, Tender Amount, and PIN Debitfield (if required). Payment Network (25.5) obtains approval from thePayment Account Issuer using Step (25.25); Payment Account Issuer may beone of an issuing bank or alternative payment issuer such as PayPal orBitcoin. After receiving approval from the Payment Account Issuer,Payment Network (25.5) sends Issuer Approval Message to Payment Acquirer(25.4) using Action Line (25.26). Acquirer (25.4) forwards the IssuerApproval Message to the POS (25.3) using Action Line (25.19) and alsoforwards the Issuer Approval Message to the SPCD (25.6) using ActionLine (25.27). The process is completed when SPCD (25.6) forwards anotification of Issuer Approval to the Mobile Device (25.2) using ActionLine (25.29).

FIG. 26 illustrates a standard POS payment flow using a debit or creditcard. For example, a Consumer (26.1) may initiate a payment transactiondepicted using action line (26.01), which causes POS (26.3) to read adebit or credit PAN number using one of a magnetic stripe or EMV format.POS device (26.3), having already calculated the total tender amount due(26.3.1), transmits the debit or credit PAN number and tender amount dueto Acquirer (26.4) as depicted by action line (26.02). Acquirer (26.4)using Step (26.03) evaluates the (previously registered) debit or creditPAN number received from POS (26.2) to determine if a MobileAuthentication is required. If a Mobile Authentication is required,Acquirer (26.4) transmits the credit or debit PAN and tender amount tothe SPCD (26.6) as depicted in action line (26.04). Using Step (26.05),SPCD (26.06) uses the credit or debit PAN number to identify the MobileDevice using the Card or Account Device Table (FIG. 53). Having nowidentified the Mobile Device, SPCD (26.6) initiates a mobileauthentication message to Mobile Device (26.2) as depicted in actionline (26.06); mobile authentication message comprised of at least thetender amount and can include other information available in theDatabase Tables (19.4.2) such as the merchant or location. Consumer(26.1) can approve the payment transaction using Mobile Device (26.2);approval (26.07) can be in the form of a Mobile PIN, biometric, or otherfactors or combinations of factors as available in and prescribed by theSettings and Database Tables (26.7). Action Line (26.08) depicts theMobile Authentication Message sent from Mobile Device (26.2) to SPCD(26.6); message comprised of one or more of a mobile PIN, tokens, andbiometric factors. Tokens may be associated with the Mobile Device andused by the SPCD to validate the device. Tokens may also be sent in lieuof sending biometric factors which may be validated locally on themobile device. SPCD (26.6) validates the Mobile Approval Message in Step(26.09); validation completed using data received in Action Line(26.10), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors including the velocity of paymenttransactions authenticated using this Mobile Device and/or registeredaccount number. Other more comprehensive rules may be applied to thetransaction as required. For example, if the card number is registeredon the PIN, Biometric Correlation Table (FIG. 62), a combination of PINand biometric factors may be required in such a way that a specificfinger must be used to enter the PIN or a part of the PIN. Havingvalidated the payment transaction, SPCD (26.6), forwards MobileAuthentication Approval Message (26.11) to Acquirer (26.4). If requiredfor the debit card based on settings, message (26.11) may include analternate PIN derived from database (26.7). Acquirer forwards PaymentTransaction including debit or credit PAN and tender amount (andalternate PIN if required) to Payment Network (26.5) using Action Line(26.12). The Payment Network (26.5) obtains approval from the PaymentAccount Issuer using Step (26.13); Payment Account Issuer may be one ofan issuing bank or alternative payment issuer such as PayPal or Bitcoin.After receiving approval from the Payment Account Issuer, PaymentNetwork (26.5) sends Issuer Approval Message to Payment Acquirer (26.4)using Action Line (26.14). Acquirer (26.4) forwards the Issuer ApprovalMessage to the POS (26.3) using Action Line (26.16) and also forwardsthe Issuer Approval Message to the SPCD (26.6) using Action Line(26.15). The process is completed when SPCD (26.6) forwards anotification of Issuer Approval to the Mobile Device (26.2) using ActionLine (26.17). Referring now to FIG. 19 in conjunction with FIG. 26,Action Line (26.02) correlates to Acquirer Network Communication Link(19.7.6); Action Line (26.04) correlates to Secure Payment NetworkCommunication Link (19.7.8); Action Line (26.06) correlates to HostCommunication Link (19.7.3) in communication with Mobile/Local Network(19.3) in communication with Mobile Communication Link (19.7.2); ActionLine (26.12) correlates to Payment Network Communication Link (19.7.5);and Action (26.13) uses Issuer Network Communication Link (19.7.7)although the Issuer is not shown in FIG. 26.

FIG. 27 illustrates an alternate standard POS payment flow using a debitor credit card. The primary difference between FIG. 26 and FIG. 27 isthe point in the flow where the Mobile Authentication is executed. Forexample, a Consumer (27.1) may initiate a payment transaction depictedusing action line (27.01), which causes POS (27.3) to read a debit orcredit PAN number using one of a magnetic stripe or EMV format. POSdevice (27.3), having already calculated the total tender amount due(27.3.1), transmits the debit or credit PAN number and tender amount dueto Acquirer (27.4) as depicted by action line (27.02). Acquirer forwardsPayment Transaction including debit or credit PAN and tender amount) toPayment Network (27.5) using Action Line (27.03). Payment Network (27.5)using Step (27.04) evaluates the (previously registered) debit or creditPAN number received from POS (27.2) to determine if a MobileAuthentication is required. If a Mobile Authentication is required,Payment Network (27.5) transmits the credit or debit PAN and tenderamount to the SPCD (27.6) as depicted in action line (27.05). Using Step(27.06), SPCD (27.6) uses the credit or debit PAN number to identify theMobile Device using the Card or Account Device Table (FIG. 53). Havingnow identified the Mobile Device, SPCD (27.6) initiates a mobileauthentication message to Mobile Device (27.2) as depicted in actionline (27.07); mobile authentication message comprised of at least thetender amount and can include other information available in andprescribed by the Settings and Database Tables (27.7). Consumer (27.1)can approve the payment transaction using Mobile Device (27.2); approval(27.08) can be in the form of a Mobile PIN, biometrics, or other factorsor combinations of factors as prescribed by or available in the Settingsand Database Tables (27.7). Action Line (27.09) depicts the MobileAuthentication Message sent from Mobile Device (27.2) to SPCD (27.6);message comprised of one or more of a mobile PIN, tokens, and biometricfactors. Tokens may be associated with the Mobile Device and used by theSPCD to validate the device. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (27.6) validates the Mobile Approval Message in Step (27.10);validation completed using data received in Action Line (27.11), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions authenticated usingthis Mobile Device and/or registered account. Other more comprehensiveauthentication rules may be applied to the transaction as required. Forexample, if the card is registered on the Registered Users, Cards, PINsTable (FIG. 44), the PIN contained in this table would be used inpreference to the default user PIN in the User PIN Table (FIG. 51).Having validated the payment transaction, SPCD (27.6), forwards MobileAuthentication Approval Message (27.12) to Acquirer (27.4). If requiredfor the debit card based on settings, message (27.12) may include analternate PIN derived from Settings and Database Tables (27.7). ThePayment Network (27.5) obtains approval from the Payment Account Issuerusing Step (27.13); Payment Account Issuer may be one of an issuing bankor alternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (27.5) sendsIssuer Approval Message to Payment Acquirer (27.4) using Action Line(27.14). Acquirer (27.4) forwards the Issuer Approval Message to the POS(27.3) using Action Line (27.16) and also forwards the Issuer ApprovalMessage to the SPCD (27.6) using Action Line (27.15). The process iscompleted when SPCD (27.6) forwards a notification of Issuer Approval tothe Mobile Device (27.2) using Action Line (27.17). Referring now toFIG. 19 in conjunction with FIG. 27, Action Line (27.02) correlates toAcquirer Network Communication Link (19.7.6); Action Line (27.05)correlates to Alternate Secure Payment Network Communication Link(19.7.4); Action Line (27.07) correlates to Host Communication Link(19.7.3) in communication with Mobile/Local Network (19.3) incommunication with Mobile Communication Link (19.7.2); Action Line(27.14) correlates to Payment Network Communication Link (19.7.5); andAction (27.13) uses Issuer Network Communication Link (19.7.7) althoughthe Issuer is not shown in FIG. 27.

FIG. 28 illustrates an enhanced POS payment flow using a debit or creditcard. For example, a Consumer (28.1) may initiate a payment transactiondepicted using action line (28.01), which causes POS (28.3) to read adebit or credit PAN number using one of a magnetic stripe or EMV format.POS device (28.3), having already calculated the total tender amount due(28.3.1), transmits the debit or credit PAN number and tender amount dueto Acquirer (28.4) as depicted by action line (28.02). Acquirer (28.4)using Step (28.03) evaluates the (previously registered) debit or creditPAN number received from POS (28.2) to determine if a MobileAuthentication is required. If a Mobile Authentication is required,Acquirer (28.4) transmits the credit or debit PAN and tender amount tothe SPCD (28.6) as depicted in action line (28.04). Using Step (28.05),SPCD (28.6) uses the credit or debit PAN number to identify the MobileDevice using the Card or Account Device Table (FIG. 53). Having nowidentified the Mobile Device, SPCD (28.6) reads the authenticationsettings for the registered debit or credit card from the Settings &Database Tables (28.7). SPCD (28.6) using step (28.07) initiates amobile authentication request message to Mobile Device (28.2) asdepicted in action line (28.08); mobile authentication request messagecomprised of at least the tender amount and can include otherauthentication requests such as the merchant, terminal or location.Consumer (28.1) can approve the payment transaction using Mobile Device(28.2); approval (28.09) can be in the form of a Mobile PIN, biometric,or other factors or combinations of factors as prescribed by oravailable in the Settings and Database Tables (27.7). If required by theAuthentication Request Message (28.08), Mobile Device (28.2) using step(28.10) can read the MID and TID from the POS (28.3). Having obtainedthe MID and TID, if required by the Authentication Request Message(28.08), Mobile Device (28.2) using step (28.12) can obtain the locationusing one of Geo Services or other method such as a local beacon. Havingnow obtained all of the required authentication information, Action Line(28.13) depicts the Mobile Authentication Message sent from MobileDevice (28.2) to SPCD (28.6); message comprised of one or more of amobile PIN, tokens, and biometric factors and other requiredauthentication message including MID, TID, and Location. SPCD (28.6)validates the Mobile Approval Message in Step (28.14); validationcompleted using data received from Settings & Database Tables (28.7),data comprised of one or more of a Mobile PIN, tokens, biometrics, orother factors including the velocity of payment transactionsauthenticated using this Mobile Device and/or registered account number.If required by the Settings & Database (28.7), the SPCD (28.6) cancompare the MID and TID obtained from the POS (28.3) to the MID and TIDobtained from Mobile Device (28.2). SPCD (28.6) may also validate thelocation received from Mobile Device (28.2) to the stored location onfile for the valid MID, TID combination. Other more comprehensive rulesmay be applied to the transaction as required. For example, if the cardis registered in the Registered Card Locations Table (FIG. 46) and thecurrent merchant location is prohibited, the transaction will berejected, irrespective of other successful criteria having beensupplied. Having validated the payment transaction, SPCD (28.6),forwards Mobile Authentication Approval Message (28.15) to Acquirer(28.4). If required for the debit card based on settings, message(28.15) may include an alternate PIN derived from Settings & DatabaseTables (28.7). Acquirer forwards Payment Transaction including debit orcredit PAN and tender amount (and alternate PIN if required) to PaymentNetwork (28.5) using Action Line (28.16). The Payment Network (28.5)obtains approval from the Payment Account Issuer using Step (28.17);Payment Account Issuer may be one of an issuing bank or alternativepayment issuer such as PayPal or Bitcoin. After receiving approval fromthe Payment Account Issuer, Payment Network (28.5) sends Issuer ApprovalMessage to Payment Acquirer (28.4) using Action Line (28.18). Acquirer(28.4) forwards the Issuer Approval Message to the POS (28.3) usingAction Line (28.19) and also forwards the Issuer Approval Message to theSPCD (28.6) using Action Line (28.20). The process is completed whenSPCD (28.6) forwards a notification of Issuer Approval to the MobileDevice (28.2) using Action Line (28.21).

FIG. 29 illustrates an alternate enhanced POS payment flow using a debitor credit card. For example, a Consumer (28.1) may initiate a paymenttransaction depicted using action line (29.01), which causes POS (29.3)to read a debit or credit PAN number using one of a magnetic stripe orEMV format. POS device (29.3), having already calculated the totaltender amount due (29.3.1), transmits the debit or credit PAN number andtender amount due to Acquirer (29.4) as depicted by action line (29.02).Acquirer (29.4) using Step (29.03) evaluates the (previously registered)debit or credit PAN number received from POS (29.2) to determine if aMobile Authentication is required. If a Mobile Authentication isrequired, Acquirer (29.4) transmits the credit or debit PAN and tenderamount to the SPCD (29.6) as depicted in action line (29.04). Using Step(29.05), SPCD (29.6) uses the credit or debit PAN number to identify theMobile Device using the Card or Account Device Table (FIG. 53). Havingnow identified the Mobile Device, SPCD (29.6) reads the authenticationsettings for the registered debit or credit card from the Settings &Database Tables (29.7). SPCD (29.6) using step (29.07) initiates amobile authentication request message to Mobile Device (29.2) asdepicted in action line (29.08); mobile authentication request messagecomprised of at least the tender amount and can include otherauthentication requests such as the merchant, terminal or location.Consumer (29.1) can approve the payment transaction using Mobile Device(29.2); approval (29.09) can be in the form of a Mobile PIN, biometric,or other factors or combinations of factors as prescribed by oravailable in the Settings and Database Tables (29.7). If required by theAuthentication Request Message (29.08), Mobile Device (29.2) using step(29.10) can read the MID and TID from the POS (29.3). Having obtainedthe MID and TID, if required by the Authentication Request Message(29.08), Mobile Device (29.2) using step (29.12) can obtain the locationusing one of Geo Services or other method such as a local beacon. Havingnow obtained all of the required authentication information, Action Line(29.13) depicts the Mobile Authentication Message sent from MobileDevice (29.2) to SPCD (29.6); message comprised of one or more of amobile PIN, tokens, and biometric factors and other requiredauthentication message including MID, TID, and Location. SPCD (29.6)validates the Mobile Approval Message in Step (29.14); validationcompleted using data received from Settings & Database Tables (29.7),data comprised of one or more of a Mobile PIN, tokens, biometrics, orother factors such as the velocity of payment transactions authenticatedusing this Mobile Device and/or registered account number. If requiredby the Settings & Database Tables (29.7), the SPCD (29.6) can comparethe MID and TID obtained from the POS (29.3) to the MID and TID obtainedfrom Mobile Device (29.2). SPCD (29.6) may also validate the locationreceived from Mobile Device (29.2) to the stored location on file forthe valid MID, TID combination. Other more comprehensive rules may beapplied to the transaction as required. For example, if the user hasregistered a card or account PIN in the Card or Account PIN Table (FIG.52), this PIN will be used in preference to the default PIN. Havingvalidated the payment transaction, SPCD (29.6), forwards MobileAuthentication Approval Message (29.15) to Acquirer (29.4). If requiredfor the debit card based on settings, message (29.15) may include analternate PIN derived from Settings & Database Tables (29.7). Acquirerforwards Payment Transaction including debit or credit PAN and tenderamount (and alternate PIN if required) to Payment Network (29.5) usingAction Line (29.16). The Payment Network (29.5) obtains approval fromthe Payment Account Issuer using Step (29.17); Payment Account Issuermay be one of an issuing bank or alternative payment issuer such asPayPal or Bitcoin. After receiving approval from the Payment AccountIssuer, Payment Network (29.5) sends Issuer Approval Message to PaymentAcquirer (29.4) using Action Line (29.18). Acquirer (29.4) forwards theIssuer Approval Message to the POS (29.3) using Action Line (29.19) andalso forwards the Issuer Approval Message to the SPCD (29.6) usingAction Line (29.20). The process is completed when SPCD (29.6) forwardsa notification of Issuer Approval to the Mobile Device (29.2) usingAction Line (29.21).

FIG. 30 illustrates a standard eCommerce payment flow using a mobilePAN. For example, a Consumer (30.1) may initiate a payment transactiondepicted using action line (30.01), which causes Mobile Device (30.2) toread a static Mobile PAN number or generate a dynamic Mobile PAN number.If Mobile Device (30.2) is configured with a static Mobile PAN number,Step (30.02) will read the previously stored static Mobile PAN.Alternatively, if Mobile Device (30.2) is configured to generate adynamic Mobile PAN, Step (30.02) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Actionline (30.03) depicts the provisioning of the Mobile PAN number alongwith the registered address associated with the Mobile Device (30.2) toeCommerce Site (30.3). The provisioning of the Mobile PAN number andaddress can be completed using one of https or other suitable securecommunication protocol using a browser or Mobile Wallet operable toconnect to eCommerce Site (30.3). The eCommerce accepts the Mobile PANnumber and address provisioned from Mobile Device (30.2) using Step(30.04). eCommerce site having already calculated the total tenderamount due (30.3.1), transmits the Mobile PAN number, address and tenderamount due to Acquirer (30.4) as depicted by action line (30.05).Acquirer (30.4) using Step (30.06) evaluates the Mobile PAN number fromeCommerce site (30.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Acquirer (30.4)transmits the Mobile PAN, address and tender amount to the SPCD (30.6)as depicted in action line (30.07). Using Step (30.08), SPCD (30.06)uses the Mobile PAN number to identify the Mobile Device (as previouslydescribed herein) and validates that the address matches the addressassociated with the mobile device. If required the SPCD (30.6) candecode a dynamic Mobile PAN number using the Host Mobile PAN Module(21.4.5) as previously described in FIG. 21. Having now identified theMobile Device, SPCD (30.6) initiates a mobile authentication message toMobile Device (30.2) as depicted in action line (30.09); mobile approvalmessage comprised of at least the tender amount and can include otherinformation available in the Settings and Database Tables (30.7).Consumer (30.1) can approve the payment transaction using Mobile Device(30.2); approval can be in the form of a Mobile PIN, biometric, or otherfactors or combinations of factors as available in and prescribed bySettings and Database Tables (30.7) Action Line (30.11) depicts theMobile Authentication Message sent from Mobile Device (30.2) to SPCD(30.6); message comprised of one or more of a mobile PIN, tokens, andbiometric factors. Tokens may be associated with the Mobile Device andused by the SPCD to validate the device. Tokens may also be associatedwith the Mobile PAN number to prevent fraudulent use of the Mobile PAN.Tokens may also be sent in lieu of sending biometric factors which maybe validated locally on the mobile device. SPCD (30.6) validates theMobile Approval Message in Step (30.13); validation completed using datareceived in Action Line (30.12), data comprised of one or more of aMobile PIN, tokens, biometrics, or other factors such as the velocity ofpayment transactions submitted using this Mobile PAN. Other morecomprehensive rules may be applied to the transaction as required. Forexample, if the Mobile PAN is registered in the Dynamic PIN, Card orAccount No. Selection Table (FIG. 60), the PIN number entered with thetransaction will determine the card number to be associated with thepayment transaction. Having approved the payment transaction for furtherprocessing, the SPCD (30.6) formats the Payment Approval Transaction byinserting a registered payment card number (e.g. Issuer PAN) or paymentaccount unique identifier (such as PayPal Account registered emailaddress or Bitcoin account no) and forwards Payment Approval Transactionto Acquirer (30.4) using Action Line (30.14). If the registered paymentcard number is one of a PIN Debit Account, payment approval data may befurther formatted to include one of an alternate PIN, partial PIN,Issuer PIN, or other approved PIN Debit field (such as a null value,sequence number, or static value) as available in and prescribed by theSettings and Database Tables (30.7). The Acquirer (30.4) receives thePayment Transaction data contained in the Payment Approval Transactionand sends Payment Transaction to the appropriate Payment Network (30.5);Payment Transaction comprised of one more of an Issuer PAN, TenderAmount, and PIN Debit field (if required). Payment Network (30.15)obtains approval from the Payment Account Issuer using Step (30.16);Payment Account Issuer may be one of an issuing bank or alternativepayment issuer such as PayPal or Bitcoin. After receiving approval fromthe Payment Account Issuer, Payment Network (30.5) sends Issuer ApprovalMessage to Payment Acquirer (30.4) using Action Line (30.17). Acquirer(30.4) forwards the Issuer Approval Message to the eCommerce Site (30.3)using Action Line (30.19) and also forwards the Issuer Approval Messageto the SPCD (30.6) using Action Line (30.18). The process is completedwhen SPCD (30.6) forwards a notification of Issuer Approval to theMobile Device (30.2) using Action Line (30.20). Referring now to FIG. 21in conjunction with FIG. 30, Action Line (30.03) correlates to LocalCommunication Link (21.7.1); Action Line (30.05) correlates to AcquirerNetwork Communication Link (21.7.6); Action Line (30.07) correlates toSecure Payment Network Communication Link (21.7.8); Action Line (30.09)correlates to Host Communication Link (21.7.3) in communication withMobile/Local Network (21.3) in communication with Mobile CommunicationLink (21.7.2); Action Line (30.15) correlates to Payment NetworkCommunication Link (21.7.5); and Action (30.16) uses Issuer NetworkCommunication Link (21.7.7) although the Issuer is not shown in FIG. 30.

FIG. 31 illustrates an alternate standard eCommerce payment flow using amobile PAN. The primary difference between FIG. 30 and FIG. 31 is thepoint in the flow where the Mobile Authentication is executed. Forexample, a Consumer (31.1) may initiate a payment transaction depictedusing action line (31.01), which causes Mobile Device (31.2) to read astatic Mobile PAN number or generate a dynamic Mobile PAN number. IfMobile Device (31.2) is configured with a static Mobile PAN number, Step(31.02) will read the previously stored Mobile PAN. Alternatively, ifMobile Device (31.2) is configured to generate a dynamic Mobile PAN,Step (31.02) will generate a dynamic Mobile PAN number using a randomvalue and defined algorithms (FIG. 72). Action line (31.03) depicts theprovisioning of the Mobile PAN number along with the registered addressassociated with the Mobile Device (31.2) to POS (31.3). The provisioningof the Mobile PAN number and address can be completed using one of httpsor other suitable secure communication protocol using a browser orMobile Wallet operable to connect to eCommerce Site (31.3). TheeCommerce Site accepts the Mobile PAN number and address provisionedfrom Mobile Device (31.2) using Step (31.04). eCommerce Site and havingalready calculated the total tender amount due (31.3.1), transmits theMobile PAN number, address, and tender amount due to Acquirer (31.4) asdepicted by action line (31.05). Acquirer forwards Payment Transactionincluding Mobile PAN, address and tender amount to Payment Network(31.5) using Action Line (31.06) Payment Network (31.5) using Step(31.07) evaluates the Mobile PAN number from eCommerce Site (31.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Payment Network (31.5) transmits the MobilePAN and tender amount to the SPCD (31.6) as depicted in action line(31.08). Using Step (31.09), SPCD (31.06) uses the Mobile PAN number toidentify the Mobile Device (see FIG. 56). If required the SPCD (31.6)can decode a dynamic Mobile PAN number using the Host Mobile PAN Module(21.4.5) as previously described in FIG. 21. Having now identified theMobile Device, SPCD (31.6) validates that the address matches theaddress associated with the mobile device and then initiates a mobileauthentication message to Mobile Device (31.2) as depicted in actionline (31.10); Mobile Approval Message comprised of at least the tenderamount and can include other information available in or required by theSettings and Database Tables (31.7). Consumer (31.1) can approve thepayment transaction using Mobile Device (31.2); approval can be in theform of a Mobile PIN, biometric, or other factors or combinations offactors as prescribed by and available in the Settings and DatabaseTables (31.7) Action Line (31.12) depicts the Mobile AuthenticationMessage sent from Mobile Device (31.2) to SPCD (31.6); message comprisedof one or more of a mobile PIN, tokens, and biometric factors. Tokensmay be associated with the Mobile Device and used by the SPCD tovalidate the device. Tokens may also be associated with the Mobile PANnumber to prevent fraudulent use of the Mobile PAN. Tokens may also besent in lieu of sending biometric factors which may be validated locallyon the mobile device. SPCD (31.6) validates the Mobile Approval Messagein Step (31.13); validation completed using data received in Action Line(31.13), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors such as the velocity of paymenttransactions submitted using this Mobile PAN. Other more comprehensiverules may be applied to the transaction as required. For example, if theCardholder has pre-registered a card or account number on the DynamicPIN Card or Account Selection Table (FIG. 60), the mobile PIN in message(31.6) is used to determine the associated Issuer PAN. Otherwise, adefault Issuer PAN may be obtained from the Mobile PAN, Card or AccountNo. Selection Table (FIG. 57). Having approved the payment transactionfor further processing, the SPCD (31.6) formats the Payment ApprovalTransaction by inserting a registered payment card number (e.g. IssuerPAN) or payment account unique identifier (such as PayPal Accountregistered email address or Bitcoin account no) and forwards PaymentApproval Transaction to Payment Network (31.5) using Action Line(31.15). If the registered payment card number is one of a PIN DebitAccount, payment approval data may be further formatted to include oneof an alternate PIN, partial PIN, Issuer PIN, or other approved PINDebit field (such as a null value, sequence number, or static value) asprescribed by and available in the Settings and Database Tables (23.7)The Payment Network (31.5) receives the Payment Transaction datacontained in the Payment Approval Transaction and Payment Network(31.16) obtains approval from the Payment Account Issuer using Step(31.16); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (31.5) sendsIssuer Approval Message to Payment Acquirer (31.4) using Action Line(31.17). Acquirer (31.4) forwards the Issuer Approval Message to theeCommerce Site (31.3) using Action Line (31.19) and also forwards theIssuer Approval Message to the SPCD (31.6) using Action Line (31.18).The process is completed when SPCD (31.6) forwards a notification ofIssuer Approval to the Mobile Device (31.2) using Action Line (31.20).

FIG. 32 illustrates an enhanced eCommerce payment flow using a mobilePAN. For example, a Consumer (32.1) may initiate a payment transactiondepicted using action line (32.01), which causes Mobile Device (32.2)using Step (32.02) to get one or more of the current location, MerchantID (MID), and Terminal ID (TID); location obtained from Geo LocationServices (21.9) or using local beacon (21.10); MID and TID obtained fromthe eCommerce site using a Browser or Mobile Wallet operable to connectto eCommerce Site (32.3) using https or other secure protocol andtransferred to Mobile Device (32.2). MID and TID may also be obtained byscanning a static or dynamic code such as a QR code displayed by theeCommerce Site. Now using Step (32.04), Mobile Device (32.2) reads astatic Mobile PAN or generates a dynamic Mobile PAN number. If MobileDevice (32.2) is configured with a static Mobile PAN number, Step(32.04) will read the previously stored Mobile PAN. Alternatively, ifMobile Device (32.2) is configured to generate a dynamic Mobile PAN,Step (32.04) will generate a dynamic Mobile PAN number using a randomvalue and defined algorithms (FIG. 72). Next, using Action Line (32.05),Mobile Device (32.02) transmits Mobile PAN, MID, TID, and Location toSPCD (32.6). SPCD (32.06) is operable to use the Mobile PAN number toidentify the Mobile Device (see FIG. 56). If required the SPCD (32.6)can decode a dynamic Mobile PAN number using the Host Mobile PAN Module(21.4.5) as previously described in FIG. 21. Having now identified theMobile Device, using Step (32.07) SPCD (32.6) reads Settings andDatabase Tables (32.7) to obtain a list of approved and disapprovedLocations, MIDs and TIDs associated with the registered Mobile PAN andusing Step (32.09) validates that the Mobile PAN may be used at thecombination of one or more of Location, MID, and TID; For example afirst Issuing Bank may prohibit a specific MID and TID to be used with apayment account while a second Issuing Bank may allow the same MID andTID. Having now validated the Location, MID, and TID in accordance withrequirements, SPCD (32.6) initiates a valid MID, TID, Location messageand transmits message using Action Line (32.10). Consumer (32.1) isnotified by Mobile Device (32.2) that the Location, TID, and MID areapproved and using Step (32.12) initiates the Mobile Payment sequence.It should be noted that the Mobile Device may be pre-configured toperform Step (32.12) thereby eliminating the need for the Consumer toinitiate the Mobile Payment sequence. Action line (32.13) depicts theprovisioning of the Mobile PAN number along with the registered addressassociated with the Mobile Device (32.2) to eCommerce Site (32.3). Theprovisioning of the Mobile PAN number and address can be completed usingone of https or other suitable secure communication protocol using aBrowser or Mobile Wallet operable to connect to eCommerce Site, (32.3).The eCommerce site accepts the Mobile PAN number and address provisionedfrom Mobile Device (32.2) using Step (32.14). eCommerce Site (32.3),having already calculated the total tender amount due (32.3.1),transmits the Mobile PAN number, address and tender amount due toAcquirer (32.4) as depicted by action line (32.15). Acquirer (32.4)using Step (32.16) evaluates the Mobile PAN number from eCommerce Site(32.2) to determine if a Mobile Authentication is required. If a MobileAuthentication is required, Acquirer (32.4) transmits the Mobile PAN andtender amount to the SPCD (32.6) as depicted in action line (32.17).Using Step (32.08), SPCD having previously identified the Mobile Device,initiates a mobile authentication message to Mobile Device (32.2) asdepicted in action line (32.18); mobile approval message comprised of atleast the tender amount and can include other information available inand prescribed by the Settings and Database Tables (32.7) such as themerchant or location. Consumer (32.1) can approve the paymenttransaction using Mobile Device (32.2); approval can be in the form of aMobile PIN, biometric, or other factors or combinations of factors asavailable in and prescribed by the Settings and Database Tables (32.7).Action Line (32.20) depicts the Mobile Authentication Message sent fromMobile Device (32.2) to SPCD (32.6); message comprised of one or more ofa mobile PIN, tokens, and biometric factors. Tokens may be associatedwith the Mobile Device and used by the SPCD to validate the device.Tokens may also be associated with the Mobile PAN number to preventfraudulent use of the Mobile PAN. Tokens may also be sent in lieu ofsending biometric factors which may be validated locally on the mobiledevice. SPCD (32.6) validates the Mobile Approval Message in Step(32.22); validation completed using data received in Action Line(32.21), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors including the registered address submittedusing this Mobile PAN. Other more comprehensive rules may be applied tothe transaction as required. For example, if the Mobile PAN isregistered on the Entity Approval Criteria Table (FIG. 58) only for useat a registered home location, the user must be at this location tocomplete the transaction. It should be noted that the Mobile ApprovalMessage depicted in Action Line (32.20) may be combined with LocationApproval Message (32.05) and that the Initiate Pay Sequence (32.12) maybe combined with Initiate Payment (32.01) thereby eliminating the needfor the Consumer to separately initiate the pay sequence (32.12). Havingapproved the payment transaction for further processing, the SPCD (32.6)formats the Payment Approval Transaction by inserting a registeredpayment card number (e.g. Issuer PAN) or payment account uniqueidentifier (such as PayPal Account registered email address or Bitcoinaccount no) and forwards Payment Approval Transaction to Acquirer (32.4)using Action Line (32.23). If the registered payment card number is oneof a PIN Debit Account, payment approval data may be further formattedto include one of an alternate PIN, partial PIN, Issuer PIN, or otherapproved PIN Debit field (such as a null value, sequence number, orstatic value) as prescribed by and available in the Settings andDatabase Tables (32.7) The Acquirer (32.4) receives the PaymentTransaction data contained in the Payment Approval Transaction and sendsPayment Transaction to the appropriate Payment Network (32.5); PaymentTransaction comprised of one more of an Issuer PAN, Tender Amount, andPIN Debit Field (if required). Payment Network (32.5) obtains approvalfrom the Payment Account Issuer using Step (32.25); Payment AccountIssuer may be one of an issuing bank or alternative payment issuer suchas PayPal or Bitcoin. After receiving approval from the Payment AccountIssuer, Payment Network (32.5) sends Issuer Approval Message to PaymentAcquirer (32.4) using Action Line (32.26). Acquirer (32.4) forwards theIssuer Approval Message to the eCommerce Site (32.3) using Action Line(32.19) and also forwards the Issuer Approval Message to the SPCD (32.6)using Action Line (32.27). The process is completed when SPCD (32.6)forwards a notification of Issuer Approval to the Mobile Device (32.2)using Action Line (32.29).

FIG. 32R illustrates a reverse eCommerce payment flow using a mobilePAN. For example, a Consumer (32R.1) may initiate a payment transactiondepicted using action line (32R.01), which causes Mobile Device (32R.2)to read a static Mobile PAN number or generate a dynamic Mobile PANnumber. If Mobile Device (32R.2) is configured with a static Mobile PANnumber, Step (32R.02) will read the previously stored static Mobile PAN.Alternatively, if Mobile Device (32R.2) is configured to generate adynamic Mobile PAN, Step (32R.02) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Actionline (32R.03) depicts the provisioning of the Mobile PAN number alongwith the registered address associated with the Mobile Device (32R.2) toeCommerce Site (32R.3). The provisioning of the Mobile PAN number andaddress can be completed using one of https or other suitable securecommunication protocol using a browser or Mobile Wallet operable toconnect to eCommerce Site (32R.3). The eCommerce site accepts the MobilePAN number and address provisioned from Mobile Device (32R.2) using Step(32R.04). eCommerce site (32R.3), having already calculated the totaltender amount due (32R.3.1), transmits the Mobile PAN number, addressand tender amount due and shipping address to Acquirer (32R.4) asdepicted by action line (32R.05). Acquirer (32R.4) using Step (32R.06)evaluates the Mobile PAN number from eCommerce site (32R.2) to determineif a Mobile Authentication is required. If a Mobile Authentication isrequired, Acquirer (32R.4) transmits the Mobile PAN and tender amount tothe SPCD (32R.6) as depicted in action line (32R.07). Using Step(32R.08), SPCD (32R.06) uses the Mobile PAN number to identify theMobile Device (see FIG. 56). If required the SPCD (32R.6) can decode adynamic Mobile PAN number using the Host Mobile PAN Module (21.4.5) aspreviously described in FIG. 21. Having now identified the MobileDevice, using Step (32R.08) SPCD (32.6) reads Settings and DatabaseTables (32R.7) using step (32R.09) to obtain a list of approved anddisapproved Locations and other authentication requirements for MobilePAN. Having now identified the authentication requirements (step 32R.10)for this Mobile PAN, SPCD (32R.6) validates the address (step 32R.11)received from the eCommerce Site to the approved address on file forMobile PAN and initiates a mobile authentication message to MobileDevice (32R.2) as depicted in action line (32R.12); mobile approvalmessage comprised of at least the tender amount and can include otherinformation available in the Settings and Database Tables (32R.7).Consumer (32R.1) can approve the payment transaction using Mobile Device(32R.2); approval can be in the form of a Mobile PIN, biometric, orother factors or combinations of factors as available in and prescribedby Settings and Database Tables (32R.7) Action Line (32R.13) depicts theentry of the required authentication elements by Consumer (32R.1). Instep 32R.14, Mobile Device determines its current location; locationobtained from Geo Location Services (21.9) or local beacon (21.10).Having now obtained the required authentication elements and the currentlocation, the Mobile Authentication Message is sent from Mobile Device(32R.2) to SPCD (32R.6) as shown in Action Line (32R.15); messagecomprised of one or more of a mobile PIN, tokens, and biometric factorstokens, and biometric factors and location indicator comprised of one ofa registered Location ID or equivalent latitude and longitude. SPCD(32R.6) validates the Mobile Approval Message in Step (32R.17);validation completed using data received in Action Line (32R.16), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions submitted usingthis Mobile PAN. Other more comprehensive rules may be applied to thetransaction as required. For example, if the Mobile PAN is registered onthe Dynamic Card Selection Table (FIG. 59), when used at an eCommerceSite, a specific payment card number could be associated with thisMobile PAN. Alternatively, if the same Mobile PAN were later used at anATM, a different card could be associated with this Mobile PAN. Havingapproved the payment transaction for further processing, the SPCD(32R.6) formats the Payment Approval Transaction by inserting aregistered payment card number (e.g. Issuer PAN) or payment accountunique identifier (such as PayPal Account registered email address orBitcoin account no) and forwards Payment Approval Transaction to PaymentNetwork (32R.5) using Action Line (32R.18). If the registered paymentcard number is one of a PIN Debit Account, payment approval data may befurther formatted to include one of an alternate PIN, partial PIN,Issuer PIN, or other approved PIN Debit field (such as a null value,sequence number, or static value) as available in and prescribed by theSettings and Database Tables (32R.7). The Payment Network (32R.5)receives the Payment Transaction data contained in the Payment ApprovalTransaction and obtains approval from the Payment Account Issuer usingStep (32R.19); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (32R.5) sendsIssuer Approval Message to SPCD (32R.6) using Action Line (32R.20). SPCD(32R.6) generates a mobile approval code (step 32R.21) and forwards theIssuer Approval Message with mobile approval code to the Acquirer(32R.4) using Action Line (32R.22). and also forwards the IssuerApproval Message with mobile approval code to the Mobile Device (32R.2)using Action Line (32R.23). Consumer (32R.1) enters the mobile approvalcode into the eCommerce Site (32R.2) shown in Action Line (32R.24).eCommerce Site (32R.3) forwards mobile approval code to Acquirer (32R.4)as shown in Action Line (32R.25). In Step (32R.26) the Acquirer (32R.5)validates the mobile approval code by comparing the mobile approval codereceived from the SPCD (32R.6) to the mobile approval code received fromthe eCommerce Site (32R.3) The process is completed when Acquirer(32R.5) forwards a notification of Issuer Approval to the eCommerce Site(32R.3) using Action Line (32R.27).

FIG. 33 illustrates an alternate enhanced eCommerce payment flow using amobile PAN. For example, a Consumer (33.1) may initiate a paymenttransaction depicted using action line (33.01), which causes MobileDevice (33.2) using Step (33.02) to get one or more of the currentlocation, Merchant ID (MID), and Terminal ID (TID); location obtainedfrom Geo Location Services (21.9) or local beacon (21.10); MID and TIDobtained from the eCommerce Site (33.3) using https or other secureprotocol and transferred to Mobile Device (33.2). Now using Step(33.04), Mobile Device (33.2) reads or generates a Mobile PAN number. IfMobile Device (33.2) is configured with a static Mobile PAN number, Step(33.04) will read the previously stored Mobile PAN. Alternatively, ifMobile Device (33.2) is configured to generate a dynamic Mobile PAN,Step (33.04) will generate a dynamic Mobile PAN number using a randomvalue and defined algorithms (FIG. 72). Next, using Action Line (33.05),Mobile Device (33.02) transmits Mobile PAN, MID, TID, and Location toSPCD (33.6). SPCD (33.06) is operable to use the Mobile PAN number toidentify the Mobile Device (see FIG. 56). If required the SPCD (33.6)can decode a dynamic Mobile PAN number using the Host Mobile PAN Module(21.4.5) as previously described in FIG. 21. Having now identified theMobile Device, using Step (33.07) SPCD (33.6) reads Settings andDatabase Tables (33.7) to obtain a list of approved and disapprovedLocations, MIDs and TIDs associated with the registered Mobile PAN andusing Step (33.09) validates that the Mobile PAN may be used at thecombination of one or more of Location, MID, and TID; combinationrequirements determined by the Settings Tables and actual combinationsdetermined by the Database Tables. For example a first Issuing Bank mayrequire all three elements to be present in order to approve a paymenttransaction while a second Issuing Bank may only require one or twoelements as a prerequisite to approval. Having now validated theLocation, MID, and TID in accordance with requirements, SPCD (33.6)initiates a valid MID, TID, Location message and transmits message usingAction Line (33.10). Consumer (33.1) is notified by Mobile Device (33.2)that the Location, TID, and MID are approved and using Step (33.12)initiates the Mobile Payment sequence. It should be noted that theMobile Device may be pre-configured to automatically perform Step(33.12) thereby eliminating the need for the Consumer to initiate theMobile Payment sequence. Action line (33.13) depicts the provisioning ofthe Mobile PAN number along with the registered address associated withthe Mobile Device (33.2) using a browser or Mobile Wallet operable toconnect to eCommerce Site (33.3). The provisioning of the Mobile PAN andaddress number can be completed using one of https or other suitablesecure communication protocol. eCommerce Site (33.3) accepts the MobilePAN number and address provisioned from Mobile Device (33.2) using Step(33.14). eCommerce Site (33.3), having already calculated the totaltender amount due (33.3.1), transmits the Mobile PAN number, address andtender amount due to Acquirer (33.4) and as depicted by action line(33.15) Acquirer routes transaction to Payment Network (33.5). PaymentNetwork (33.5) using Step (33.16) evaluates the Mobile PAN number fromeCommerce Site (33.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Acquirer (33.5)transmits the Mobile PAN and tender amount to the SPCD (33.6) asdepicted in action line (33.17). Using Step (33.08), SPCD havingpreviously identified the Mobile Device, validates that the addressmatches the address associated with the mobile device and then initiatesa mobile authentication message to Mobile Device (33.2) as depicted inaction line (33.18); mobile approval message is comprised of at leastthe tender amount and can include other information available in andprescribed by the Settings and Database Tables (33.7). Consumer (33.1)can approve the payment transaction using Mobile Device (33.2); approvalcan be in the form of a Mobile PIN, biometric, or other factors orcombinations of factors as prescribed by the Settings Tables) and basedon information stored in the Database Tables (19.4.2). Action Line(33.20) depicts the Mobile Authentication Message sent from MobileDevice (33.2) to SPCD (33.6); message comprised of one or more of amobile PIN, tokens, and biometric factors. Tokens may be associated withthe Mobile Device and used by the SPCD to validate the device. Tokensmay also be associated with the Mobile PAN number to prevent fraudulentuse of the Mobile PAN. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (33.6) validates the Mobile Approval Message in Step (33.22);validation completed using data received in Action Line (33.21), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions submitted usingthis Mobile PAN. Other more comprehensive rules may be applied to thetransaction as required. For example, the current location can bedetermined using the Registered Locations Table (FIG. 47) using anavailable beacon ID or geo coordinates. If the Consumer haspre-registered approved or rejected locations as exemplified on theRegistered Users, Locations Table (FIG. 45), the transaction can beapproved for further processing or simply rejected based on thelocation. It should be noted that the Mobile Approval Message depictedin Action Line (33.20) may be combined with Location Approval Message(33.05) and that the Initiate Pay Sequence (33.12) may be combined withInitiate Payment (33.01) thereby eliminating the need for the Consumerto separately initiate the pay sequence (33.12). Having approved thepayment transaction for further processing, the SPCD (33.6) formats thePayment Approval Transaction by inserting a registered payment cardnumber (e.g. Issuer PAN) or payment account unique identifier (such asPayPal Account registered email address or Bitcoin account no) andforwards Payment Approval Transaction to Acquirer (33.4) using ActionLine (33.23). If the registered payment card number is one of a PINDebit Account, payment approval data may be further formatted to includeone of an alternate PIN, partial PIN, Issuer PIN, or other approved PINDebit field (such as a null value, sequence number, or static value) asprescribed by and available in the Settings and Data Base Tables (33.7).The Payment Network (33.5) receives the Payment Transaction datacontained in the Payment Approval Transaction and sends PaymentTransaction to the appropriate Issuer for approval; Payment Transactioncomprised of one more of an Issuer PAN, Tender Amount, and PIN Debitfield (if required). Payment Network (33.5) obtains approval from thePayment Account Issuer using Step (33.25); Payment Account Issuer may beone of an issuing bank or alternative payment issuer such as PayPal orBitcoin. After receiving approval from the Payment Account Issuer,Payment Network (33.5) sends Issuer Approval Message to Payment Acquirer(33.4) using Action Line (33.26). Acquirer (33.4) forwards the IssuerApproval Message to the eCommerce Site (33.3) using Action Line (33.19)and also forwards the Issuer Approval Message to the SPCD (33.6) usingAction Line (33.27). The process is completed when SPCD (33.6) forwardsa notification of Issuer Approval to the Mobile Device (33.2) usingAction Line (33.29).

FIG. 34 illustrates a standard ATM transaction flow using a mobile PAN.For example, a Consumer (34.1) may initiate a cash withdrawaltransaction depicted using action line (34.01), which causes MobileDevice (34.2) to read a static Mobile PAN number or generate a dynamicMobile PAN number. If Mobile Device (34.2) is configured with a staticMobile PAN number, Step (34.02) will read the previously stored staticMobile PAN. Alternatively, if Mobile Device (34.2) is configured togenerate a dynamic Mobile PAN, Step (34.02) will generate a dynamicMobile PAN number using a random value and defined algorithms (FIG. 72).Action line (34.03) depicts the provisioning of the Mobile PAN numberfrom Mobile Device (34.2) to ATM (34.3). The provisioning of the MobilePAN number and transaction amount can be completed using one of amanual, NFC, BLE, RFID, QR Code or other suitable communicationprotocol. ATM (34.3) accepts the Mobile PAN number provisioned fromMobile Device (34.2) using Step (34.04). ATM (34.3), having alreadyaccepted the total transaction amount (34.3.1), transmits the Mobile PANnumber and transaction amount to Bank or Merchant Acquirer (34.4) asdepicted by action line (34.05). Bank or Merchant Acquirer (34.4) usingStep (34.06) evaluates the Mobile PAN number from ATM (34.3) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Bank or Merchant Acquirer (34.4) transmitsthe Mobile PAN and tender amount to the SPCD (34.6) as depicted inaction line (34.07). Using Step (34.08), SPCD (34.06) uses the MobilePAN number to identify the Mobile Device (see FIG. 56). If required theSPCD (34.6) can decode a dynamic Mobile PAN number using the Host MobilePAN Module (20.4.5) as previously described in FIG. 20. Having nowidentified the Mobile Device, SPCD (34.6) initiates a mobileauthentication message to Mobile Device (34.2) as depicted in actionline (34.09); mobile approval message comprised of at least thetransaction amount and can include other information as prescribed by oravailable in the Settings and Database Tables (34.7). Consumer (34.1)can approve the transaction using Mobile Device (34.2); approval can bein the form of a Mobile PIN, biometric, or other factors or combinationsof factors as prescribed by or available in the Settings and DatabaseTables (34.7). Action Line (34.11) depicts the Mobile AuthenticationMessage sent from Mobile Device (34.2) to SPCD (34.6); message comprisedof one or more of a mobile PIN, tokens, and biometric factors. Tokensmay be associated with the Mobile Device and used by the SPCD tovalidate the device. Tokens may also be associated with the Mobile PANnumber to prevent fraudulent use of the Mobile PAN. Tokens may also besent in lieu of sending biometric factors which may be validated locallyon the mobile device. SPCD (34.6) validates the Mobile Approval Messagein Step (34.13); validation completed using data received in Action Line(34.12), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors such as the velocity of paymenttransactions submitted using this Mobile PAN. Other more comprehensiverules may be applied to the transaction as required. For example, ifthere are more than one registered device on file associated with theregistered card number, a different PIN can be associated with eachregistered device on the Card Mobile PIN Table (FIG. 52). If forexample, an iPhone 27 is used as the mobile device, a first registeredPIN would be required. Alternatively, if a Android phone 53 is used asthe mobile device, a second registered PIN would be required, Havingapproved the payment transaction for further processing, the SPCD (34.6)formats the Payment Approval Transaction by inserting a registeredpayment card number (e.g. Issuer PAN) or payment account uniqueidentifier (such as PayPal Account registered email address or Bitcoinaccount no) and forwards Payment Approval Transaction to Bank orMerchant Acquirer (34.4) using Action Line (34.14). If the registeredpayment card number is one of a PIN Debit Account, payment approval datamay be further formatted to include one of an alternate PIN, partialPIN, Issuer PIN, or other approved PIN Debit field (such as a nullvalue, sequence number, or static value) as prescribed by and availablein the Settings and Database Tables (34.7). The Acquirer (34.4) receivesthe Payment Transaction using contained in the Payment ApprovalTransaction and sends Payment Transaction to the appropriate PaymentNetwork (34.5); Payment Transaction comprised of one more of an IssuerPAN, Transaction Amount, and PIN Debit Field (if required). PaymentNetwork (34.15) obtains approval from the Payment Account Issuer usingStep (34.16); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (34.5) sendsIssuer Approval Message to Payment Acquirer (34.4) using Action Line(34.17). Bank or Merchant Acquirer (34.4) forwards the Issuer ApprovalMessage to the ATM (34.3) using Action Line (34.19) and also forwardsthe Issuer Approval Message to the SPCD (34.6) using Action Line(34.18). The process is completed when SPCD (34.6) forwards anotification of Issuer Approval to the Mobile Device (34.2) using ActionLine (34.20). Referring now to FIG. 20 in conjunction with FIG. 34,Action Line (34.03) correlates to Local Communication Link (20.7.1);Action Line (34.05) correlates to Acquirer Network Communication Link(20.7.6); Action Line (34.07) correlates to Secure Payment NetworkCommunication Link (20.7.8); Action Line (34.09) correlates to HostCommunication Link (20.7.3) in communication with Mobile/Local Network(20.3) in communication with Mobile Communication Link (20.7.2); ActionLine (34.15) correlates to Payment Network Communication Link (20.7.5);and Action (34.16) uses Issuer Network Communication Link (20.7.7)although the Issuer is not shown in FIG. 34.

FIG. 35 illustrates an alternate standard ATM transaction flow using amobile PAN. The primary difference between FIG. 34 and FIG. 35 is thepoint in the flow where the Mobile Authentication is executed. Forexample, a Consumer (35.1) may initiate a withdrawal transactiondepicted using action line (35.01), which causes Mobile Device (35.2) toread a static Mobile PAN number or generate a dynamic Mobile PAN number.If Mobile Device (35.2) is configured with a static Mobile PAN number,Step (35.02) will read the previously stored Mobile PAN. Alternatively,if Mobile Device (35.2) is configured to generate a dynamic Mobile PAN,Step (35.02) will generate a dynamic Mobile PAN number using a randomvalue and defined algorithms (FIG. 72). Action line (35.03) depicts theprovisioning of the Mobile PAN number and transaction amount from MobileDevice (35.2) to ATM (35.3). The provisioning of the Mobile PAN numberand transaction amount can be completed using one of a manual, NFC, BLE,RFID, QR Code or other suitable communication protocol. ATM (35.3)accepts the Mobile PAN number provisioned from Mobile Device (35.2)using Step (35.04). ATM device (35.3), having already received the totaltransaction amount (35.3.1), transmits the Mobile PAN number andtransaction amount to Bank or Merchant Acquirer (35.4) as depicted byaction line (35.05). Bank or Merchant Acquirer forwards PaymentTransaction including Mobile PAN and transaction amount to PaymentNetwork (35.5) using Action Line (35.06) Payment Network (35.5) usingStep (35.07) evaluates the Mobile PAN number from ATM (35.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Payment Network (35.5) transmits the MobilePAN and tender amount to the SPCD (35.6) as depicted in action line(35.08). Using Step (35.09), SPCD (35.06) uses the Mobile PAN number toidentify the Mobile Device (see FIG. 56). If required the SPCD (35.6)can decode a dynamic Mobile PAN number using the Host Mobile PAN Module(20.4.5) as previously described in FIG. 20. Having now identified theMobile Device, SPCD (35.6) initiates a mobile authentication message toMobile Device (35.2) as depicted in action line (35.10); Mobile ApprovalMessage comprised of at least the transaction amount and can includeother information as prescribed by or available in the Settings andDatabase Tables (35.7). Consumer (35.1) can approve the paymenttransaction using Mobile Device (35.2); approval can be in the form of aMobile PIN, biometric, or other factors or combinations of factors asprescribed by or available in the Settings and Database Tables (35.7).Action Line (35.12) depicts the Mobile Authentication Message sent fromMobile Device (35.2) to SPCD (35.6); message comprised of one or more ofa mobile PIN, tokens, and biometric factors. Tokens may be associatedwith the Mobile Device and used by the SPCD to validate the device.Tokens may also be associated with the Mobile PAN number to preventfraudulent use of the Mobile PAN. Tokens may also be sent in lieu ofsending biometric factors which may be validated locally on the mobiledevice. SPCD (35.6) validates the Mobile Approval Message in Step(35.13); validation completed using data received in Action Line(35.13), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors including the velocity of paymenttransactions submitted using this Mobile PAN. Other more comprehensiverules may be applied to the transaction as required. For example, theSPDS can use the Mobile PAN from the payment transaction in Step (35.07)to evaluate if there is a specific default card number to be used withthis Mobile PAN when used at an ATM machine. This method is furtherdescribed in FIG. 59. Having approved the payment transaction forfurther processing, the SPCD (35.6) formats the Payment ApprovalTransaction by inserting a registered payment card number (e.g. IssuerPAN) or payment account unique identifier (such as PayPal Accountregistered email address or Bitcoin account no) and forwards PaymentApproval Transaction to Payment Network (35.5) using Action Line(35.15). If the registered payment card number is one of a PIN DebitAccount, payment approval data may be further formatted to include oneof an alternate PIN, partial PIN, Issuer PIN, or other approved PINDebit field (such as a null value, sequence number, or static value) asprescribed by and available in the Settings and Database Tables (35.7).The Payment Network (35.5) receives the Payment Transaction datacontained in the Payment Approval Transaction and Payment Network(35.16) obtains approval from the Payment Account Issuer using Step(35.16); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (35.5) sendsIssuer Approval Message to Payment Bank or Merchant Acquirer (35.4)using Action Line (35.17). Bank or Merchant Acquirer (35.4) forwards theIssuer Approval Message to the ATM (35.3) using Action Line (35.19) andalso forwards the Issuer Approval Message to the SPCD (35.6) usingAction Line (35.18). The process is completed when SPCD (35.6) forwardsa notification of Issuer Approval to the Mobile Device (35.2) usingAction Line (35.20). Referring now to FIG. 20 in conjunction with FIG.25, Action Line (35.03) correlates to Local Communication Link (20.7.1);Action Line (35.05) correlates to Acquirer Network Communication Link(20.7.6); Action Line (35.08) correlates to Alternate Secure PaymentNetwork Communication Link (20.7.4); Action Line (35.10) correlates toHost Communication Link (20.7.3) in communication with Mobile/LocalNetwork (20.3) in communication with Mobile Communication Link (20.7.2);Action Line (35.17) correlates to Payment Network Communication Link(20.7.5); and Action (35.16) uses Issuer Network Communication Link(20.7.7) although the Issuer is not shown in FIG. 35.

FIG. 36 illustrates an enhanced ATM transaction flow using a mobile PAN.For example, a Consumer (36.1) may initiate a payment transactiondepicted using action line (36.01), which causes Mobile Device (36.2)using Step (36.02) to get one or more of the current location, MerchantID (MID), and Terminal ID (TID); location obtained from Geo LocationServices (20.9) or local beacon (20.10); MID and TID obtained from theATM (36.3) using one of RFID, BLE, or other similar method andtransferred to Mobile Device (36.2). MID and TID may also be obtained byscanning a static or dynamic code such as a QR code. Now using Step(36.04), Mobile Device (36.2) reads a static Mobile PAN or generates adynamic Mobile PAN number. If Mobile Device (36.2) is configured with astatic Mobile PAN number, Step (36.04) will read the previously storedMobile PAN. Alternatively, if Mobile Device (36.2) is configured togenerate a dynamic Mobile PAN, Step (36.04) will generate a dynamicMobile PAN number using a random value and defined algorithms (FIG. 72).Next, using Action Line (36.05), Mobile Device (36.02) transmits MobilePAN, MID, TID, and Location to SPCD (36.6). SPCD (36.06) is operable touse the Mobile PAN number to identify the Mobile Device (see FIG. 56).If required the SPCD (36.6) can decode a dynamic Mobile PAN number usingthe Host Mobile PAN Module (20.4.5) as previously described in FIG. 20.Having now identified the Mobile Device, using Step (36.07) SPCD (36.6)reads Settings and Database Tables (36.7) to obtain a list of approvedand disapproved Locations, MIDs and TIDs associated with the registeredMobile PAN and using Step (36.09) validates that the Mobile PAN may beused at the combination of one or more of Location, MID, and TID. Havingnow validated the Location, MID, and TID in accordance withrequirements, SPCD (36.6) initiates a valid MID, TID, Location messageand transmits message using Action Line (36.10). Consumer (36.1) isnotified by Mobile Device (36.2) that the Location, TID, and MID areapproved and using Step (36.12) initiates the Mobile Payment sequence.It should be noted that the Mobile Device may be pre-configured toperform Step (36.12) thereby eliminating the need for the Consumer toinitiate the Mobile Payment sequence. Action line (36.13) depicts theprovisioning of the Mobile PAN number from Mobile Device (36.2) to ATM(36.3). The provisioning of the Mobile PAN number can be completed usingone of a manual, NFC, BLE, RFID, QR Code or other suitable communicationprotocol. ATM (36.3) accepts the Mobile PAN number provisioned fromMobile Device (36.2) using Step (36.14). POS device (36.3), havingalready accepted the transaction amount (36.3.1), transmits the MobilePAN number and tender amount to Bank or Merchant Acquirer (36.4) asdepicted by action line (36.15). Bank or Merchant Acquirer (36.4) usingStep (36.16) evaluates the Mobile PAN number from ATM (36.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Bank or Merchant Acquirer (36.4) transmitsthe Mobile PAN and transaction amount to the SPCD (36.6) as depicted inaction line (36.17). Using Step (36.08), SPCD having previouslyidentified the Mobile Device, initiates a mobile authentication messageto Mobile Device (36.2) as depicted in action line (36.18); mobileapproval message comprised of at least the transaction amount and caninclude other information as prescribed by or available in the Settingsand Database Tables (36.7). Consumer (36.1) can approve the transactionusing Mobile Device (36.2); approval can be in the form of a Mobile PIN,biometric, or other factors or combinations of factors as prescribed byor available in the Settings and Database Tables (36.7). Action Line(36.20) depicts the Mobile Authentication Message sent from MobileDevice (36.2) to SPCD (36.6); message comprised of one or more of amobile PIN, tokens, and biometric factors. Tokens may be associated withthe Mobile Device and used by the SPCD to validate the device. Tokensmay also be associated with the Mobile PAN number to prevent fraudulentuse of the Mobile PAN. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (36.6) validates the Mobile Approval Message in Step (36.22);validation completed using data received in Action Line (36.21), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors including the velocity of payment transactions submitted usingthis Mobile PAN. It should be noted that the Mobile Approval Messagedepicted in Action Line (36.20) may be combined with Location ApprovalMessage (36.05) and that the Initiate Pay Sequence (36.12) may becombined with Initiate Payment (36.01) thereby eliminating the need forthe Consumer to separately initiate the pay sequence (36.12). Other morecomprehensive rules may be applied to the transaction as required. Forexample, if the Mobile PAN is registered on the Venue Biometric Table(FIG. 61) a voice approval may be required for transactions that exceeda specific amount. Having approved the payment transaction for furtherprocessing, the SPCD (36.6) formats the Payment Approval Transaction byinserting a registered payment card number (e.g. Issuer PAN) or paymentaccount unique identifier (such as PayPal Account registered emailaddress or Bitcoin account no) and forwards Payment Approval Transactionto Bank or Merchant Acquirer (36.4) using Action Line (36.23). If theregistered payment card number is one of a PIN Debit Account, paymentapproval data may be further formatted to include one of an alternatePIN, partial PIN, Issuer PIN, or other approved PIN Debit field (such asa null value, sequence number, or static value) as prescribed by theSettings (19.4.1) and available in Database Tables (19.4.2). The Bank orMerchant Acquirer (36.4) receives the Payment Transaction data containedin the Payment Approval Transaction and sends Payment Transaction to theappropriate Payment Network (36.5); Payment Transaction comprised of onemore of an Issuer PAN, Tender Amount, and PIN Debit Field (if required).Payment Network (36.5) obtains approval from the Payment Account Issuerusing Step (36.25); Payment Account Issuer may be one of an issuing bankor alternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (36.5) sendsIssuer Approval Message to Payment Acquirer (36.4) using Action Line(36.26). Bank or Merchant Acquirer (36.4) forwards the Issuer ApprovalMessage to the POS (36.3) using Action Line (36.19) and also forwardsthe Issuer Approval Message to the SPCD (36.6) using Action Line(36.27). The process is completed when SPCD (36.6) forwards anotification of Issuer Approval to the Mobile Device (36.2) using ActionLine (36.29).

FIG. 36R illustrates a reverse ATM transaction flow using a mobile PAN.For example, a Consumer (36R.1) may initiate a payment transactiondepicted using action line (36R.01), which causes Mobile Device (36R.2)to read a static Mobile PAN number or generate a dynamic Mobile PANnumber. If Mobile Device (36R.2) is configured with a static Mobile PANnumber, Step (36R.02) will read the previously stored static Mobile PAN.Alternatively, if Mobile Device (36R.2) is configured to generate adynamic Mobile PAN, Step (36R.02) will generate a dynamic Mobile PANnumber using a random value and defined algorithms (FIG. 72). Actionline (36R.03) depicts the provisioning of the Mobile PAN number fromMobile Device (36R.2) to ATM (36R.3). The provisioning of the Mobile PANnumber can be completed using one of a manual, NFC, BLE, RFID, QR Codeor other suitable communication protocol. ATM (36R.3) accepts the MobilePAN number provisioned from Mobile Device (36R.2) using Step (36R.04).ATM (36R.3), having already calculated the total tender amount due(36R.3.1), transmits the Mobile PAN number and tender amount due to Bankor Merchant (36R.4) as depicted by action line (36R.05). Bank orMerchant (36R.4) using Step (36R.06) evaluates the Mobile PAN numberfrom ATM (36R.2) to determine if a Mobile Authentication is required. Ifa Mobile Authentication is required, Acquirer (36R.4) transmits theMobile PAN and tender amount to the SPCD (36R.6) as depicted in actionline (36R.07). Using Step (36R.08), SPCD (36R.06) uses the Mobile PANnumber to identify the Mobile Device (see FIG. 56). If required the SPCD(36R.6) can decode a dynamic Mobile PAN number using the Host Mobile PANModule (20.4.5) as previously described in FIG. 20. Having nowidentified the Mobile Device, using Step (36R.08) SPCD (36R.6) readsSettings and Database Tables (36R.7) using step (36R.09) to obtain alist of approved and disapproved Locations and other authenticationrequirements for Mobile PAN. Having now identified the authenticationrequirements (step 36R.10) for this Mobile PAN, SPCD (36R.6) (using step36R.11) initiates a mobile authentication message to Mobile Device(36R.2) as depicted in action line (36R.12); mobile approval messagecomprised of at least the tender amount and can include otherinformation available in the Settings and Database Tables (36R.7).Consumer (36R.1) can approve the payment transaction using Mobile Device(36R.2); approval can be in the form of a Mobile PIN, biometric, orother factors or combinations of factors as available in and prescribedby Settings and Database Tables (36R.7) Action Line (36R.13) depicts theentry of the required authentication elements by Consumer (36R.1). Ifadditional biometric authentication is required by the SPCD inaccordance with the settings, these factors are provided in connectionwith 36R.13 a and 36R13 b. Biometric factors may be provided actively bythe Consumer (36R.1) using a wearable device or the Mobile Device(36R.2) or a combination thereof. Alternatively, the Biometric factorsmay be provided in a passive manner by the Consumer whereby data istransmitted from a wearable device to one of the ATM (36R.3) or to theMobile Device (36R.2). Support for the communication of biometric data,either passive or active, is found in FIG. 20. Referring to FIG. 20,wearable devices (20.11) are operable to transmit biometric data usingone or both of wireless links (20.11.1) and (20.11.2). In step 32R.14,Mobile Device determines its current location; location obtained fromGeo Location Services (20.9) or local beacon (20.10). Having nowobtained the required authentication elements and the current location,the Mobile Authentication Message is sent from Mobile Device (36R.2) toSPCD (36R.6) as shown in Action Line (36R.15); message comprised of oneor more of a mobile PIN, tokens, and biometric factors and locationindicator comprised of one of a registered Location ID and/or equivalentlatitude and longitude. If additional biometric data has been collectedby ATM 36R.3 using step 36R13.b, this data is transmitted to the SPCDusing Action Line (36R13.b). SPCD (36R.6) validates the Mobile ApprovalMessage in Step (36R.17); validation completed using data received inAction Line (36R.16), data comprised of one or more of a Mobile PIN,tokens, biometrics, or other factors such as the velocity of paymenttransactions submitted using this Mobile PAN. Other more comprehensiverules may be applied to the transaction as required. For example, if theMobile PAN is registered on the Venue, Biometric Table (FIG. 61) for useat an ATM wherein a specific dollar threshold is exceeded such as$1,000, multiple biometric factors may be required to approve thetransaction. In this scenario, the SPCD is operable to require themultiple biometric factors as a condition to transaction approval.Having approved the payment transaction for further processing, the SPCD(36R.6) formats the Payment Approval Transaction by inserting aregistered payment card number (e.g. Issuer PAN) or payment accountunique identifier (such as PayPal Account registered email address orBitcoin account no) and forwards Payment Approval Transaction to PaymentNetwork (36R.5) using Action Line (36R.18). If the registered paymentcard number is one of a PIN Debit Account, payment approval data may befurther formatted to include one of an alternate PIN, partial PIN,Issuer PIN, or other approved PIN Debit field (such as a null value,sequence number, or static value) as available in and prescribed by theSettings and Database Tables (36R.7). The Payment Network (36R.5)receives the Payment Transaction data contained in the Payment ApprovalTransaction and obtains approval from the Payment Account Issuer usingStep (36R.19); Payment Account Issuer may be one of an issuing bank oralternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (36R.5) sendsIssuer Approval Message to SPCD (36R.6) using Action Line (36R.20). SPCD(36R.6) generates a mobile approval code (step 32R.21) and forwards theIssuer Approval Message with mobile approval code to the Acquirer(36R.4) using Action Line (36R.22) and also forwards the Issuer ApprovalMessage with mobile approval code to the Mobile Device (36R.2) usingAction Line (36R.23). Consumer (36R.1) either enters the mobile approvalcode into the ATM (36R.2) shown in Action Line (36R.24) or mobileapproval code is transmitted to ATMA™ device using one of NFC, RFID,BLE, or QR code. ATM (36R.3) forwards mobile approval code to Acquirer(36R.4) as shown in Action Line (36R.25). In Step (36R.26) the Acquirer(36R.5) validates the mobile approval code by comparing the mobileapproval code received from the SPCD (36R.6) to the mobile approval codereceived from the ATM (36R.3) The process is completed when Acquirer(36R.5) forwards a notification of Issuer Approval to the ATM (36R.3)using Action Line (36R.27).

FIG. 37 illustrates an alternate enhanced ATM transaction flow using amobile PAN For example, a Consumer (37.1) may initiate a withdrawaltransaction depicted using action line (37.01), which causes MobileDevice (37.2) using Step (37.02) to get one or more of the currentlocation, Merchant ID (MID), and Terminal ID (TID); location obtainedfrom Geo Location Services (20.9) or local beacon (20.10); MID and TIDobtained from the ATM (37.3) using one of RFID, BLE or other similarmethod and transferred to Mobile Device (37.2). Now using Step (37.04),Mobile Device (37.2) reads or generates a Mobile PAN number. If MobileDevice (37.2) is configured with a static Mobile PAN number, Step(37.04) will read the previously stored Mobile PAN. Alternatively, ifMobile Device (37.2) is configured to generate a dynamic Mobile PAN,Step (37.04) will generate a dynamic Mobile PAN number using a randomvalue and defined algorithms (FIG. 72). Next, using Action Line (37.05),Mobile Device (37.02) transmits Mobile PAN, MID, TID, and Location toSPCD (37.6). SPCD (37.6) is operable to use the Mobile PAN number toidentify the Mobile Device (see FIG. 56). If required the SPCD (37.6)can decode a dynamic Mobile PAN number using the Host Mobile PAN Module(20.4.5) as previously described in FIG. 20. Having now identified theMobile Device, using Step (37.07) SPCD (37.6) reads Settings andDatabase Tables (37.7) to obtain a list of approved and disapprovedLocations, MIDs and TIDs associated with the registered Mobile PAN andusing Step (37.09) validates that the Mobile PAN may be used at thecombination of one or more of Location, MID, and TID; combinationrequirements determined by the Settings Tables and actual combinationsdetermined by the Database Tables. For example a first Issuing Bank mayrequire all three elements to be present in order to approve a paymenttransaction while a second Issuing Bank may only require one or twoelements as a prerequisite to approval. Having now validated theLocation, MID, and TID in accordance with requirements, SPCD (37.6)initiates a valid MID, TID, Location message and transmits message usingAction Line (37.10). Consumer (37.1) is notified by Mobile Device (37.2)that the Location, TID, and MID are approved and using Step (37.12)initiates the Mobile Payment sequence. It should be noted that theMobile Device may be pre-configured to automatically perform Step(37.12) thereby eliminating the need for the Consumer to initiate theMobile Payment sequence. Action line (37.13) depicts the provisioning ofthe Mobile PAN number from Mobile Device (37.2) to ATM (37.3). Theprovisioning of the Mobile PAN number can be completed using one of amanual, NFC, BLE, RFID, QR Code or other suitable communicationprotocol. ATM (37.3) accepts the Mobile PAN number provisioned fromMobile Device (37.2) using Step (37.14). ATM device (37.3), havingalready received the total transaction amount (37.3.1), transmits theMobile PAN number and transaction amount to Bank or Merchant Acquirer(37.4) and as depicted by action line (37.15) Bank or Merchant Acquirerroutes transaction to Payment Network (37.5). Payment Network (37.5)using Step (37.16) evaluates the Mobile PAN number from ATM (37.2) todetermine if a Mobile Authentication is required. If a MobileAuthentication is required, Bank or Merchant Acquirer (37.5) transmitsthe Mobile PAN and tender amount to the SPCD (37.6) as depicted inaction line (37.17). Using Step (37.08), SPCD having previouslyidentified the Mobile Device, initiates a mobile authentication messageto Mobile Device (37.2) as depicted in action line (37.18); mobileapproval message is comprised of at least the tender amount and caninclude other information as prescribed by or available in the Settingsand Database Tables (37.7). Consumer (37.1) can approve the paymenttransaction using Mobile Device (37.2); approval can be in the form of aMobile PIN, biometric, or other factors or combinations of factors asprescribed by or available in the Settings and Database Tables (37.7).Action Line (37.20) depicts the Mobile Authentication Message sent fromMobile Device (37.2) to SPCD (37.6); message comprised of one or more ofa mobile PIN, tokens, and biometric factors. Tokens may be associatedwith the Mobile Device and used by the SPCD to validate the device.Tokens may also be associated with the Mobile PAN number to preventfraudulent use of the Mobile PAN. Tokens may also be sent in lieu ofsending biometric factors which may be validated locally on the mobiledevice. SPCD (37.6) validates the Mobile Approval Message in Step(37.22); validation completed using data received in Action Line(37.21), data comprised of one or more of a Mobile PIN, tokens,biometrics, or other factors including the velocity of paymenttransactions submitted using this Mobile PAN. It should be noted thatthe Mobile Approval Message depicted in Action Line (37.20) may becombined with Location Approval Message (37.05) and that the InitiatePay Sequence (37.12) may be combined with Initiate Payment (37.01)thereby eliminating the need for the Consumer to separately initiate thepay sequence (37.12). Other more comprehensive rules may be applied tothe transaction as required. For example, if a Mobile PAN has beenpre-registered with a specific Mobile using the Mobile PAN, Device,Mobile PIN Table (FIG. 56) the validation of message (37.6) can includea determination that the token matches the registered token incombination with the other data elements including the Mobile PIN,Mobile PAN Token, and Device Token. Having approved the paymenttransaction for further processing, the SPCD (37.6) formats the PaymentApproval Transaction by inserting a registered payment card number (e.g.Issuer PAN) or payment account unique identifier (such as PayPal Accountregistered email address or Bitcoin account no) and forwards PaymentApproval Transaction to Bank or Merchant Acquirer (37.4) using ActionLine (37.23). If the registered payment card number is one of a PINDebit Account, payment approval data may be further formatted to includeone of an alternate PIN, partial PIN, Issuer PIN, or other approved PINDebit field (such as a null value, sequence number, or static value) asprescribed by or available in the Settings and Database Tables (37.7).The Payment Network (37.5) receives the Payment Transaction datacontained in the Payment Approval Transaction and sends PaymentTransaction to the appropriate Issuer for approval; Payment Transactioncomprised of one more of an Issuer PAN, Tender Amount, and PIN Debitfield (if required). Payment Network (37.5) obtains approval from thePayment Account Issuer using Step (37.25); Payment Account Issuer may beone of an issuing bank or alternative payment issuer such as PayPal orBitcoin. After receiving approval from the Payment Account Issuer,Payment Network (37.5) sends Issuer Approval Message to Payment Bank orMerchant Acquirer (37.4) using Action Line (37.26). Bank or MerchantAcquirer (37.4) forwards the Issuer Approval Message to the ATM (37.3)using Action Line (37.19) and also forwards the Issuer Approval Messageto the SPCD (37.6) using Action Line (37.27). The process is completedwhen SPCD (37.6) forwards a notification of Issuer Approval to theMobile Device (37.2) using Action Line (37.29).

FIG. 38 illustrates a standard ATM transaction flow using a debit orcredit card. For example, a Consumer (38.1) may initiate a transactiondepicted using action line (38.01), which causes ATM (38.3) to read adebit or credit PAN number using one of a magnetic stripe or EMV format.ATM device (38.3), having already accepted the total transaction amount(38.3.1), transmits the debit or credit PAN number and transactionamount to Bank or Merchant Acquirer (38.4) as depicted by action line(38.02). Bank or Merchant Acquirer (38.4) using Step (38.03) evaluatesthe (previously registered) debit or credit PAN number received from ATM(38.2) to determine if a Mobile Authentication is required. If a MobileAuthentication is required, Bank or Merchant Acquirer (38.4) transmitsthe credit or debit PAN and tender amount to the SPCD (38.6) as depictedin action line (38.04). Using Step (38.05), SPCD (38.6) uses the creditor debit PAN number to identify the Mobile Device using the Card orAccount Device Table (FIG. 53). Having now identified the Mobile Device,SPCD (38.6) initiates a mobile authentication message to Mobile Device(38.2) as depicted in action line (38.06); mobile authentication messagecomprised of at least the tender amount and can include otherinformation as prescribed by and available in the Settings and DatabaseTables (38.7). Consumer (38.1) can approve the payment transaction usingMobile Device (38.2); approval (38.07) can be in the form of a MobilePIN, biometric, or other factors or combinations of factors asprescribed by and available in the Settings and Database Tables (38.7).Action Line (38.08) depicts the Mobile Authentication Message sent fromMobile Device (38.2) to SPCD (38.6); message comprised of one or more ofa mobile PIN, tokens, and biometric factors. Tokens may be associatedwith the Mobile Device and used by the SPCD to validate the device.Tokens may also be sent in lieu of sending biometric factors which maybe validated locally on the mobile device. SPCD (38.6) validates theMobile Approval Message in Step (38.09); validation completed using datareceived in Action Line (38.10), data comprised of one or more of aMobile PIN, tokens, biometrics, or other factors such as the velocity ofpayment transactions authenticated using this Mobile Device and/orregistered account number. Other more comprehensive rules may be appliedto the transaction as required. For example, if the Debit or Credit PANnumber is listed on the Card Mobile PIN Table (FIG. 52) the SPDS canvalidate that the correct Mobile PIN is used with the designated MobileDevice. An iPhone 27 for example may require a different password versusand Android phone 53 for the given Debit or Credit PAN number. Havingvalidated the payment transaction, SPCD (38.6), forwards MobileAuthentication Approval Message (38.11) to Bank or Merchant Acquirer(38.4). If required for the debit card based on settings, message(38.11) may include an alternate PIN derived from database (38.7). Bankor Merchant Acquirer forwards Payment Transaction including debit orcredit PAN and tender amount (and alternate PIN if required) to PaymentNetwork (38.5) using Action Line (38.12). The Payment Network (38.5)obtains approval from the Payment Account Issuer using Step (38.13);Payment Account Issuer may be one of an issuing bank or alternativepayment issuer such as PayPal or Bitcoin. After receiving approval fromthe Payment Account Issuer, Payment Network (38.5) sends Issuer ApprovalMessage to Payment Bank or Merchant Acquirer (38.4) using Action Line(38.14). Bank or Merchant Acquirer (38.4) forwards the Issuer ApprovalMessage to the ATM (38.3) using Action Line (38.16) and also forwardsthe Issuer Approval Message to the SPCD (38.6) using Action Line(38.15). The process is completed when SPCD (38.6) forwards anotification of Issuer Approval to the Mobile Device (38.2) using ActionLine (38.17). Referring now to FIG. 20 in conjunction with FIG. 38,Action Line (38.02) correlates to Acquirer Network Communication Link(20.7.6); Action Line (38.04) correlates to Secure Payment NetworkCommunication Link (20.7.8); Action Line (38.06) correlates to HostCommunication Link (20.7.3) in communication with Mobile/Local Network(20.3) in communication with Mobile Communication Link (20.7.2); ActionLine (38.12) correlates to Payment Network Communication Link (20.7.5);and Action (38.13) uses Issuer Network Communication Link (20.7.7)although the Issuer is not shown in FIG. 38.

FIG. 39 illustrates an alternate standard ATM transaction flow using adebit or credit card. The primary difference between FIG. 38 and FIG. 39is the point in the flow where the Mobile Authentication is executed.For example, a Consumer (39.1) may initiate a payment transactiondepicted using action line (39.01), which causes ATM (39.3) to read adebit or credit PAN number using one of a magnetic stripe or EMV format.ATM device (39.3), having already accepted the total transaction amount(39.3.1), transmits the debit or credit PAN number and transactionamount to Bank or Merchant Acquirer (39.4) as depicted by action line(39.02). Bank or Merchant Acquirer forwards Payment Transactionincluding debit or credit PAN and transaction amount) to Payment Network(39.5) using Action Line (39.03). Payment Network (39.5) using Step(39.04) evaluates the (previously registered) debit or credit PAN numberreceived from ATM (39.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Payment Network (39.5)transmits the credit or debit PAN and transaction amount to the SPCD(39.6) as depicted in action line (39.05). Using Step (39.06), SPCD(39.6) uses the credit or debit PAN number to identify the Mobile Deviceusing the Card or Account Device Table (FIG. 53). Having now identifiedthe Mobile Device, SPCD (39.6) initiates a mobile authentication messageto Mobile Device (39.2) as depicted in action line (39.07); mobileauthentication message comprised of at least the tender amount and caninclude other information as prescribed by and available in the Settingsand Database Tables (39.07). Consumer (39.1) can approve the paymenttransaction using Mobile Device (39.2); approval (39.08) can be in theform of a Mobile PIN, biometric, or other factors or combinations offactors as prescribed by and available in the Settings and DatabaseTables (39.7). Action Line (39.09) depicts the Mobile AuthenticationMessage sent from Mobile Device (39.2) to SPCD (39.6); message comprisedof one or more of a mobile PIN, tokens, and biometric factors. Tokensmay be associated with the Mobile Device and used by the SPCD tovalidate the device. Tokens may also be sent in lieu of sendingbiometric factors which may be validated locally on the mobile device.SPCD (39.6) validates the Mobile Approval Message in Step (39.10);validation completed using data received in Action Line (39.11), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions authenticated usingthis Mobile Device and/or registered account number. Other morecomprehensive rules may be applied to the transaction as required andpreviously discussed herein. For example, if the card is registered onthe Registered Users, Cards, PINs Table (FIG. 44), the PIN contained inthis table would be used in preference to the default user PIN in theUser PIN Table (FIG. 51). Having validated the payment transaction, SPCD(39.6), forwards Mobile Authentication Approval Message (39.12) to Bankor Merchant Acquirer (39.4). If required for the debit card based onsettings, message (39.12) may include an alternate PIN derived fromdatabase (39.7). The Payment Network (39.5) obtains approval from thePayment Account Issuer using Step (39.13); Payment Account Issuer may beone of an issuing bank or alternative payment issuer such as PayPal orBitcoin. After receiving approval from the Payment Account Issuer,Payment Network (39.5) sends Issuer Approval Message to Payment Bank orMerchant Acquirer (39.4) using Action Line (39.14). Bank or MerchantAcquirer (39.4) forwards the Issuer Approval Message to the ATM (39.3)using Action Line (39.16) and also forwards the Issuer Approval Messageto the SPCD (39.6) using Action Line (39.15). The process is completedwhen SPCD (39.6) forwards a notification of Issuer Approval to theMobile Device (39.2) using Action Line (39.17). Referring now to FIG. 20in conjunction with FIG. 39, Action Line (39.02) correlates to AcquirerNetwork Communication Link (20.7.6); Action Line (39.05) correlates toAlternate Secure Payment Network Communication Link (20.7.4); ActionLine (39.07) correlates to Host Communication Link (20.7.3) incommunication with Mobile/Local Network (20.3) in communication withMobile Communication Link (20.7.2); Action Line (39.14) correlates toPayment Network Communication Link (20.7.5); and Action (39.13) usesIssuer Network Communication Link (20.7.7) although the Issuer is notshown in FIG. 39.

FIG. 40 illustrates an enhanced ATM transaction flow using a debit orcredit card. For example, a Consumer (40.1) may initiate a transactiondepicted using action line (40.01), which causes ATM (40.3) to read adebit or credit PAN number using one of a magnetic stripe or

EMV format. ATM device (40.3), having already received the totaltransaction amount (40.3.1), transmits the debit or credit PAN numberand transaction amount to Bank or Merchant Acquirer (40.4) as depictedby action line (40.02). Bank or Merchant Acquirer (40.4) using Step(40.03) evaluates the (previously registered) debit or credit PAN numberreceived from ATM (40.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Bank or MerchantAcquirer (40.4) transmits the credit or debit PAN and transaction amountto the SPCD (40.6) as depicted in action line (40.04). Using Step(40.05), SPCD (40.6) uses the credit or debit PAN number to identify theMobile Device using the Card or Account Device Table (FIG. 53). Havingnow identified the Mobile Device, SPCD (40.6) reads the authenticationsettings for the registered debit or credit card from the Settings &Database Tables (40.7). SPCD (40.6) using step (40.07) initiates amobile authentication request message to Mobile Device (40.2) asdepicted in action line (40.08); mobile authentication request messagecomprised of at least the transaction amount and can include otherauthentication requests such as the merchant, terminal or location.Consumer (40.1) can approve the payment transaction using Mobile Device(40.2); approval (40.09) can be in the form of a Mobile PIN, biometric,or other factors or combinations of factors as prescribed by andavailable in the Settings and Database Tables (40.7). If required by theAuthentication Request Message (40.08), Mobile Device (40.2) using step(40.10) can read the MID and TID from the ATM (40.3). Having obtainedthe MID and TID, if required by the Authentication Request Message(40.08), Mobile Device (40.2) using step (40.12) can obtain the locationusing one of Geo Services or other method such as a local beacon. Havingnow obtained all of the required authentication information, Action Line(40.13) depicts the Mobile Authentication Message sent from MobileDevice (40.2) to SPCD (40.6); message comprised of one or more of amobile PIN, tokens, and biometric factors and other requiredauthentication message including MID, TID, and Location. SPCD (40.6)validates the Mobile Approval Message in Step (40.14); validationcompleted using data received from Settings & Database (40.7), datacomprised of one or more of a Mobile PIN, tokens, biometrics, or otherfactors such as the velocity of payment transactions authenticated usingthis Mobile Device and/or registered account number. If required by theSettings & Database Tables (40.7), the SPCD (40.6) can compare the MIDand TID obtained from the ATM (40.3) to the MID and TID obtained fromMobile Device (40.2). SPCD (40.6) may also validate the locationreceived from Mobile Device (40.2) to the stored location on file forthe valid MID, TID combination. Other more comprehensive rules may beapplied to the transaction as required. For example, if the card numberis registered on the Venue Biometric Table (FIG. 61), a heart ratereading may be required from a registered wearable device fortransactions over a specific amount at a specific location.Alternatively, an iris scan may be required from a different registeredwearable device for transactions at a specific location or within aprescribed time range. Having validated the payment transaction, SPCD(40.6), forwards Mobile Authentication Approval Message (40.15) to Bankor Merchant Acquirer (40.4). If required for the debit card based onsettings, message (40.15) may include an alternate PIN derived fromSettings & Database Tables (40.7). Bank or Merchant Acquirer forwardsPayment Transaction including debit or credit PAN and transaction amount(and alternate PIN if required) to Payment Network (40.5) using ActionLine (40.16). The Payment Network (40.5) obtains approval from thePayment Account Issuer using Step (40.17); Payment Account Issuer may beone of an issuing bank or alternative payment issuer such as PayPal orBitcoin. After receiving approval from the Payment Account Issuer,Payment Network (40.5) sends Issuer Approval Message to Payment Bank orMerchant Acquirer (40.4) using Action Line (40.18). Bank or MerchantAcquirer (40.4) forwards the Issuer Approval Message to the ATM (40.3)using Action Line (40.19) and also forwards the Issuer Approval Messageto the SPCD (40.6) using Action Line (40.20). The process is completedwhen SPCD (40.6) forwards a notification of Issuer Approval to theMobile Device (40.2) using Action Line (40.21).

FIG. 41 illustrates an alternate enhanced ATM transaction flow using adebit or credit card. For example, a Consumer (41.1) may initiate atransaction depicted using action line (41.01), which causes ATM (41.3)to read a debit or credit PAN number using one of a magnetic stripe orEMV format. ATM device (41.3), having already received the totaltransaction amount (41.3.1), transmits the debit or credit PAN numberand transaction amount to Bank or Merchant Acquirer (41.4) as depictedby action line (41.02). Bank or Merchant Acquirer (41.4) using Step(41.03) evaluates the (previously registered) debit or credit PAN numberreceived from ATM (41.2) to determine if a Mobile Authentication isrequired. If a Mobile Authentication is required, Bank or MerchantAcquirer (41.4) transmits the credit or debit PAN and transaction amountto the SPCD (41.6) as depicted in action line (41.04). Using Step(41.05), SPCD (41.6) uses the credit or debit PAN number to identify theMobile Device using the Card or Account Device Table (FIG. 53). Havingnow identified the Mobile Device, SPCD (41.6) reads the authenticationsettings for the registered debit or credit card from the Settings &Database Tables (41.7). SPCD (41.6) using step (41.07) initiates amobile authentication request message to Mobile Device (41.2) asdepicted in action line (41.08); mobile authentication request messagecomprised of at least the transaction amount and can include otherauthentication requests such as the merchant, terminal or location.Consumer (41.1) can approve the payment transaction using Mobile Device(41.2); approval (41.09) can be in the form of a Mobile PIN, biometric,or other factors or combinations of factors as prescribed by andavailable in the Settings and Database Tables (41.7). If required by theAuthentication Request Message (41.08), Mobile Device (41.2) using step(41.10) can read the MID and TID from the ATM (41.3). Having obtainedthe MID and TID, if required by the Authentication Request Message(41.08), Mobile Device (41.2) using step (41.12) can obtain the locationusing one of Geo Services or other method such as a local beacon. Havingnow obtained all of the required authentication information, Action Line(41.13) depicts the Mobile Authentication Message sent from MobileDevice (41.2) to SPCD (41.6); message comprised of one or more of amobile PIN, tokens, and biometric factors and other requiredauthentication message including MID, TID, and Location. SPCD (41.6)validates the Mobile Approval Message in Step (41.14); validationcompleted using data received from Settings & Database Tables (41.7),data comprised of one or more of a Mobile PIN, tokens, biometrics, orother factors such as the velocity of payment transactions authenticatedusing this Mobile Device and/or registered account number. If requiredby the Settings & Database Tables (41.7), the SPCD (41.6) can comparethe MID and TID obtained from the ATM (41.3) to the MID and TID obtainedfrom Mobile Device (41.2). SPCD (41.6) may also validate the locationreceived from Mobile Device (41.2) to the stored location on file forthe valid MID, TID combination. Other more comprehensive rules may beapplied to the transaction as required. For example, if the Mobile PANis registered in the Venue Biometric Table (FIG. 61), there might be arequirement for multiple biometric factors to be collected and validatedin connection with this transaction. In this scenario, the SPCD willrequire and validate multiple biometric factors which may be receivedfrom a single device or from a variety of source devices such aswearable devices as required by the Venue Biometric Table (FIG. 61).Having validated the payment transaction, SPCD (41.6), forwards MobileAuthentication Approval Message (41.15) to Bank or Merchant Acquirer(41.4). If required for the debit card based on settings, message(41.15) may include an alternate PIN derived from Settings & DatabaseTables (41.7). Bank or Merchant Acquirer forwards Payment Transactionincluding debit or credit PAN and transaction amount (and alternate PINif required) to Payment Network (41.5) using Action Line (41.16). ThePayment Network (41.5) obtains approval from the Payment Account Issuerusing Step (41.17); Payment Account Issuer may be one of an issuing bankor alternative payment issuer such as PayPal or Bitcoin. After receivingapproval from the Payment Account Issuer, Payment Network (41.5) sendsIssuer Approval Message to Bank or Merchant Acquirer (41.4) using ActionLine (41.18). Bank or Merchant Acquirer (41.4) forwards the IssuerApproval Message to the ATM (41.3) using Action Line (41.19) and alsoforwards the Issuer Approval Message to the SPCD (41.6) using ActionLine (41.20). The process is completed when SPCD (41.6) forwards anotification of Issuer Approval to the Mobile Device (41.2) using ActionLine (41.21).

FIG. 42 illustrates a registered cards and accounts table. This tablecontains a row for every registered payment card (or payment account).Exemplary columns include the card (or account) number, card (oraccount) type, brand (affiliated network), issuing entity, expirationdate, and other related columns as appropriate. Account types mayinclude traditional credit or debit card accounts, DDA accounts, MobileStored Value Accounts (SVA), and alternate accounts such as Bitcoin.Accounts may also be non-payment accounts such as accounts that areassociated with health records, insurance policy accounts, and creditreports.

FIG. 43 illustrates a registered users table. This table contains a rowfor every registered user in the system. Exemplary columns include UserID, User Name, Address, email, and phone number.

FIG. 44 illustrates a registered users, cards, Accounts, and PINs table.This table allows users to optionally set up a separate PIN for eachregistered card or account. Exemplary columns include User ID, Card orAccount No., Card PIN, and other fields as appropriate. Data in thistable can also be used to select a payment account based on the PIN thatis entered. In this way, if a given user has registered multipleregistered payment cards, each card with a unique PIN, the PIN inputselection can be used by the system to identify the card to be used forthe current payment or transaction. Unique PINs can also be establishedfor non-payment accounts such as accounts associated with healthrecords, insurance policies, and credit reports. A social securitynumber is exemplary of a reference account associated with a creditreport.

FIG. 45 illustrates a registered users, locations table. This tableallows users to optionally white list and black list locations whichwould apply to all transactions for the user irrespective of card oraccount used. Exemplary columns include User ID, Location, Action(approve or reject), and other columns as appropriate. Typical locationswhere a consumer would approve the use of registered accounts wouldinclude their home, work, and primary doctor.

FIG. 46 illustrates a registered cards or accounts, locations table.This table allows users to optionally further control location usage atthe card or account number level. Exemplary columns include the card oraccount number, location ID, and action (approve or reject), and othercolumns as appropriate. For example, a Health Savings Account (HSA) maybe approved for the location associated with a primary doctor. But, thepayment card associated with a teenage child might be disapproved for alocal liquor store. A notification flag may be set if a card isattempted to be used in a restricted location. Specific SIC and MCCcodes may also be used in this table as general entries to prevent orallow the use of specific accounts from specific merchants associatedwith these codes. If a SIC code or MCC code is listed here in thisassociation with an account number, the SIC or MCC code is firstdetermined from Table 54, Registered Merchants. A Mobile PAN number maybe posted to this table. If a Mobile PAN number is posted to this table,it represents all of the cards and accounts associated with the MobilePAN as registered in Table 57.

FIG. 47 illustrates a registered locations table. This table containsall registered locations known to the system for all merchants, doctors,consumers and other registered locations. The data can be normalized sothat locations that are common to many users can be stored one time. Thetable includes a row for each unique location. Exemplary columns includethe latitude and longitude of registered locations, beacon ID, and otherfields as appropriate to define a unique location. It is possible that aspecific physical address with given geo coordinates may be associatedwith multiple referenced user merchant addresses. For example Location 3may be associated with both of a gas station and fast food restaurantand therefore share the same geo coordinates. However, a differentBeacon ID may be associated with each POS device in order to distinguishbetween the gas station transactions and the fast food restauranttransactions.

FIG. 48 illustrates a registered devices table. This table includes anentry for each unique registered device known by the system. The tablecontains a row for each unique device. Exemplary columns include: Devicenumber (which is assigned by the system), Device type may be one ofphone, tablet, PC, POS, ring, watch, eye glasses or other registereddevice, MSISDN (unique phone number), IMEI (a unique manufactureridentification or serial number may be stored if available), and a tokenID value may be associated with the device. The Token ID when present ina transaction may be used by the system to identify the unique device.Other fields may be stored as appropriate to identify or fingerprint aunique device.

FIG. 49 illustrates a users and devices table. This is a cross referencetable created by the system that correlates registered users anddevices. Exemplary columns include the User ID, Device ID, Priority(identifies a primary device), and other fields as appropriate tocorrelate users and devices. If multiple mobile devices are registeredand associated with a specific account on Table 52, the user number canbe Used ID (‘swilson’ for example) can be used to identify the primarydevice of the primary user associated with the registered account. Ifmultiple (two or more) devices are registered as a Primary device for agiven user and if a registered account is associated with more than onedevice on Table 52, a dual or multi authentication is required for theaccount number that is registered with multiple devices. For example,User ‘bnatural’ can register iPhone ‘99’ and Android Phone ‘88’ each asprimary device in Table 49.

FIG. 50 illustrates a device, device PIN, token table. This table allowsa unique PIN to be stored for each registered device. A token may beassociated with each PIN and stored on the table. If the PIN field isblank, the system will use the default PIN for the registered user onTable 51. If token field is blank, system will use the default devicetoken as reflected in FIG. 48.

FIG. 51 illustrates a user, PIN table. This table allows registeredusers to store a user PIN. This PIN is considered the default PIN forthe user. Default PIN is used when card specific PIN is not available orto recover a card or device PIN when forgotten.

FIG. 52 illustrates a card or account, mobile device, mobile PIN table.This table includes a row for every registered card and account in thesystem for the purpose of storing and quickly retrieving the PIN numberassociated with this card or account number when authenticated with aspecific device. An Account number may be listed multiple timesrepresenting multiple rows in this table. For example, Account Number‘3727-xxx-xxx-xxxx’ may be registered to be used with both an Android 53and iPhone 27 device. The system will use the device specified asPrimary Device in Table 49 to determine which device to use toauthenticate a specific transaction. In some exemplary use cases,multiple devices may be registered as Primary device on Table 49. In thecase where multiple devices are registered as Primary device on Table49, a dual or multi device authentication is required. For example,Account Number ‘5400-xxxx-xxxx-xxxx’ can be registered with iPhone ‘88’and Android ‘99’ on Table 52 and associated with ‘bnatural’ devicesregistered on Table 49. Account numbers may be non-payment accountsassociated with an insurance policy or credit report or othernon-payment accounts. If blank, the system will use the default PIN forthe card or account as defined in FIG. 44. If no default PIN has beenestablished for the card, the system will revert to the user's defaultPIN defined in Table 51.

FIG. 53 illustrates a card or account, device table. This table is usedby the system during transaction authentication to determine the MobileDevice associated with a card centric payment transaction. If a cardnumber is associated with more than one mobile device, a reference isposted to use Table 52. For example Account No. ‘3727-xxx-xx-xxxx’ isdirected to use Table 52 to determine the device. This table isoptionally used to limit cards and accounts to be used with specificdevices. As such, it allows users to tie specific payment accounts tospecific devices. This would prevent a card from being registered orused with another device.

FIG. 54 illustrates a registered merchant table. This table is a list ofall known merchants to the system and includes information about thetype of merchant such as MCC and SIC code. If a user wants to prevent amobile device, card or account from being used at a particular SIC codeor MCC code, the relevant code may be obtained from this table duringthe authorization process.

FIG. 55 illustrates a registered merchant, location, terminal table.Includes a list of all locations and terminals for each merchant intable 54. This table correlates the known, registered locations with theknown, registered merchants. A separate row is added for each uniqueterminal located at each location for the registered merchant.

FIG. 56 illustrates a Mobile PAN, device, mobile PIN, Mobile PAN tokentable. This table lists all registered Mobile PAN numbers, theauthorized device, a mobile PIN for each Mobile PAN, a Mobile PAN Token,a Derived Mobile PAN a Random Seed Value, and a Sequence Number. Usingthis table the SPCD can use one of a Mobile PAN, Derived (Dynamic)Mobile PAN, or Mobile PAN Token to determine the mobile deviceassociated with a transaction. A unique Mobile PAN token may be storedfor each unique Mobile PAN. Using this table, the Mobile PAN Token isassociated with the Mobile PAN along with the registered device ID and aunique Mobile PIN. For example, MPAN 10 may be associated with iPhone22, PIN No. ‘!x37’, and Mobile PAN Token ‘!@#{circumflex over( )}%$#&{circumflex over ( )}’. If the PIN number is blank, the systemwill use the Device PIN from Table 50. If the Token is blank, the systemwill use the Device Token from Table 48. Using this table, the MobilePAN Token can be validated for each transaction that uses the Mobile PANirrespective whether the Mobile PAN is of a static or dynamic type.Mobile PAN may be one of a static PAN or a Derived Dynamic Mobile PANPAN as discussed throughout this specification and in greater detail inFIGS. 19, 20, 21 and 72. The Derived Dynamic Mobile PAN is generatedusing the Static Mobile PAN and the Random Seed Value.

FIG. 57 illustrates a Mobile PAN, Card No., selection table. This tableincludes an entry for associating card and account numbers to Mobile PANnumbers. It allows the SPCD to select a card number based on the defaultsetting for the Mobile PAN. For example, MPAN 1 may be associated withDebit Account 25.

FIG. 58 illustrates an entity approval criteria table. This table allowstransactions to be accepted or approved based on a variety of criteriasuch as location and purchase amount. The table is flexible in itsdesign, allowing entries for users, cards, Mobile PANs, Devices; each anentity that can be restricted or approved by data in this table. Forexample, a specific card number ‘88’ may always be approved at location‘25’ associated with Starbucks9999 while a given user ‘22’ can neverspend more than $500 at location ‘30’ associated with ABCLiquorStore. Inanother example, a given Mobile PAN ‘15’ cannot be used to spend morethan $100 irrespective of location.

FIG. 59 illustrates a dynamic card, account selection table. This tableallows the system to select a card or account number for a given MobilePAN based on a variety of factors including the venue (ATM, eCommerce),purchase amount, Merchant Type (SIC, MCC), Merchant, Product (UPC).Using this table a payment transaction can be split between multiplecard or account numbers based on product, location or merchant. Forexample, a small business owner may shop for business supplies andpurchase a snack from the same store. The business supplies may becharged to the registered corporate card associated with the Mobile PANwhile the snack is charged to the registered personal card associatedwith the Mobile PAN. This table and process allows a single Mobile PANto be associated with and transmitted by a device (static or dynamic)while the Mobile PAN is later translated (split) into one or more cardor account numbers by the system. For example, MPAN 1, when used at anATM is associated with Card No. '77. And MPAN 5 when used to purchase aproduct with UPC ‘A’ uses default card no ‘44’ but when used to purchasea product with UPC code ‘B’ is associated with card no ‘43’. In thisexample, UPC codes A and B are only exemplary of actual UPC codes whichwould be used in implementation.

FIG. 60 illustrates a Dynamic PIN card selection table. This tableallows multiple PIN numbers to be stored for each registered Mobile PAN;mobile PIN number used by the system to select the Card or accountnumber for the payment transaction. Alternatively, a biometric factormay be registered for a selected Mobile PAN; biometric is subsequentlyused to determine card number for a given payment transaction. Forexample, a fingerprint may designate that the registered Visa card beused whereas a voice authentication may indicate that another card beselected. For example, when MPAN 1 is associated with PIN ‘12345’ CardNo 1 is selected by the SPCD for the transaction.

FIG. 61 illustrates a venue, biometric table. As referenced in FIGS. 25,36, 36R, 40, and 41, this table allows the system to require a specificform of biometric from a specific registered device for a registeredMobile PAN or card or account number based on a combination of factorsincluding venue, location, time, date, and transaction amount. Forexample, a registered Mobile PAN if used at an ATM and transactionamount is greater than $100 may require a voice authentication from theuser's phone. Another transaction initiated from an ecommerce site mayrequire another type of biometric factor such as heart rate, bodytemperature, or iris scan from another device such as a ring, watch, oreye glasses. FIG. 36R is exemplary of how biometric data may becollected in one of a passive or dynamic nature from wearable devices incommunication with an ATM or Mobile Device. The referenced example isalso applicable to FIGS. 25, 36, 40, and 41 as well as othertransactions which may require aggregate biometric factors fortransaction approval.

FIG. 62 illustrates a PIN, biometric correlation table. This tablefacilitates more granularity for authenticating PIN numbers andbiometric factors together. For example, a registered Mobile PAN mayhave an associated Pin number equal to ‘2468’ where the ‘2’ must beentered using the right index finger, the ‘4’ must be entered by theright middle finger, the ‘6’ must be entered by the right ring finger,and the ‘8’ must be entered by the left thumb. In another example, aregistered card number may have an associated Pin of ‘3579’ where avoice authentication is required in reverse order (9′,′7′,′513′). Inanother example, registered card may have an associated Pin of ‘98765’where the left index finger is required to enter only the ‘9’. Inanother exemplary embodiment, a registered Mobile PAN number may have anassociated PIN number of ‘12345’ which wherein the first four digits areentered using fingers and the last digit of ‘5’ is entered using voice.A special biometric entry user interface as further described in FIG. 63may be required to accommodate the above embodiments.

FIG. 63 illustrates the biometric entry user interface needed toaccommodate the collection of biometric factors contemporaneously incombination with PIN numbers. Mobile Device (6301) is operable toreceive approval request (6302). As shown, each position in the userinterface is operable to collect biometric information at the positionof entry. For example, a registered Mobile PAN may have an associatedPIN number equal to ‘2468’ where the ‘2’ must be entered using the rightindex finger, the ‘4’ must be entered by the right middle finger, the‘6’ must be entered by the right ring finger, and the ‘8’ must beentered by the left thumb. Position Four (6303) is intended to furtherillustrate this embodiment by expanding the fourth data entry positioncomprised within Mobile Device (6301) and clearly show the correlationof a biometric finger print entered contemporaneously with the number‘4’ associated with the second position of the PIN number ‘2,4,6,8’. Aunique token can be associated with each biometric factor during deviceregistration and stored on the Secure Element of the device. Asbiometric factors are input, they can be compared to the registeredbiometric factors already stored on the Secure Element of the device. Atoken can be associated with each registered biometric factor stored onthe Secure Element. Rather than expose the biometric factor duringtransmission to the SPCD, the token associated with the biometric factorcan be transmitted along with the corresponding PIN number. Using thismethod, each entry associated with the PIN is followed by a tokenassociated with the biometric factor. Completing the example herein, the‘2’ is followed in transmission with a token representing the registeredbiometric of the right index finger, the ‘4’ is followed in transmissionwith a token representing the registered biometric of the right middlefinger, the ‘6’ is followed in transmission by a token associated withthe registered right ring finger, and the ‘8’ is followed intransmission by a token associated with the registered left thumb.

FIG. 64 illustrates an exemplary registration flow sponsored by themerchant.

Merchant (64.20) using list of all merchant payment accounts (64.10)sends communication with offer to register a merchant payment account toaccount owners (64.30). In step (64.40) account owners may register amerchant payment or loyalty account to be stored in Database (64.50). Inthe process of registering the Payment or Loyalty Account (64.50),Account Owner may also register PIN numbers, Mobile Devices, WearableDevices, Locations, and other information related to the registeredpayment account. As shown, Mobile Device (64.90) is comprised ofRegistration Application (64.99) which is used to create New DevicesDatabase (66.80). Registration Application may be stored within SecureElement (SE). All new registration data is stored into SPCD database(6470). Registered account numbers may subsequently be transmitted byMerchant (64.20) to other entities such as Payment Networks, Acquirers,and Merchants as needed and authorized. During the device registrationprocess one or more tokens may be generated by the SPCD and transmittedto the Mobile Device. Tokens may include a Device Token, Mobile PANToken associated with a Mobile PAN. Tokens and Mobile PAN can besecurely stored on device file system or into a Secure Element (SE)comprised within the device. During the registration process, AccountOwner can register one or more biometric factors to be used inconnection with accounts and transactions. These biometric factors maybe stored locally on the device or biometric factors may be transmittedto the SPCD. Locally stored biometric factors can be stored on devicefile system or into a Secure Element comprised within the device. Atoken can be associated with each stored biometric factor, stored on thedevice SE, and transmitted to the SPCD during registration. Foradditional security and to prevent a secure element from being moved toanother device, a unique identifier such as an IMEI or Serial No. can bederived from the device, hashed, and stored within the Secure Elementcomprised within the device.

FIG. 65 illustrates an exemplary registration flow sponsored by thepayment account issuer. Account Issuer (65.20) using list of all paymentaccounts (65.10) sends communication with offer to register paymentaccount to Account Owners (65.30). In step (65.40) Account Owners mayregister Payment Account to be stored in Database (65.50). In theprocess of registering the Payment Account (65.50), Account Owner mayalso register PIN numbers, Mobile Devices, Wearable Devices, Locations,Merchants and other information related to the registered paymentaccount and as previously described in the Figures and exemplary tables.As shown, Mobile Device (65.90) is comprised of Registration Application(65.99) which is used to create New Devices Database (65.80). All newregistration data is stored into SPCD database (6470). RegistrationApplication may be stored within Secure Element (SE). All newregistration data is stored into SPCD database (65.70). Registeredaccount numbers may subsequently be transmitted by Account Issuer toother entities such as Payment Networks, Acquirers, Merchants upon theregistration of a mobile device, During the device registration processone or more tokens may be generated by the SPCD and transmitted to theMobile Device. Tokens may include a Device Token, Mobile PAN Token,associated with a Mobile PAN. Tokens and Mobile PAN can be securelystored on device file system or into a Secure Element (SE) comprisedwithin the device. During the registration process, Account Owner canregister one or more biometric factors to be used in connection withaccounts and transactions. These biometric factors may be stored locallyon the device or biometric factors may be transmitted to the SPCD.Locally stored biometric factors can be stored on device file system orinto a Secure Element comprised within the device. A token can beassociated with each stored biometric factor, stored on the device SEand transmitted to the SPCD. For additional security and to prevent asecure element from being moved to another device, a unique identifiersuch as an IMEI or Serial No. can be derived from the device, hashed,and stored within the Secure Element comprised within the device.

FIG. 66 illustrates an exemplary registration flow initiated by theconsumer to register a plurality of accounts which may include payment,insurance, credit, medical and other accounts. Consumer (66.10) mayinteract with Portal (66.30) to enter account information which isstored in New Account Table (66.30). Consumer may also register one ormore devices using Registration Application (66.99) comprised withinMobile Device (66.50). For additional security Registration Applicationmay be stored within Secure Element (SE) Mobile Device (66.50) may befurther operable to access Web Portal (66.10) for account registrationpurposes. New Account (65.30) and New Devices (66.60) are input to theSecure Payment Computing Device (66.70) which updates SPCD Settings andTables (66.80). During the registration process, one or more of tokens,Mobile PANs are securely transmitted to the newly registered mobiledevices. During the device registration process one or more tokens maybe generated by the SPCD and transmitted to the Mobile Device. Tokensmay include a Device Token, Mobile PAN Token, associated with a MobilePAN. Tokens and Mobile PAN can be securely stored on device file systemor into a Secure Element (SE) comprised within the device. During theregistration process, Account Owner can register one or more biometricfactors to be used in connection with accounts and transactions. Thesebiometric factors may be stored locally on the device or biometricfactors may be transmitted to the SPCD. Locally stored biometric factorscan be stored on device file system or into a Secure Element comprisedwithin the device. A token can be associated with each stored biometricfactor, stored on the device SE and transmitted to the SPCD. Foradditional security and to prevent a secure element from being moved toanother device, a unique identifier such as an IMEI or Serial No. can bederived from the device, hashed, and stored within the Secure Elementcomprised within the device.

FIG. 67 illustrates an exemplary registration flow sponsored by aninsurance company. Insurance company (67.20) using list of all insuranceaccounts (67.10) sends communication with offer to register insuranceaccount to Account Owners (67.30). In step (67.40) Account Owners mayregister insurance account to be stored in Database (67.50). In theprocess of registering the Payment Account (67.50), Account Owner mayalso register PIN numbers, Mobile Devices, Wearable Devices, Locations,Doctors, Hospitals, Drug Stores and other information related to theregistered insurance account and as previously described in the Figuresand exemplary tables. As shown, Mobile Device (67.90) is comprised ofRegistration Application (67.99) which is used to create New DevicesDatabase (67.80). Registration Application may be stored within SecureElement (SE). All new registration data is stored into SPCD database(65.70). Registered account numbers may be subsequently transmitted byinsurance company to other entities such as hospitals, drug stores uponthe registration of a mobile device. During the device registrationprocess one or more tokens may be generated by the SPCD and transmittedto the Mobile Device. Tokens may include a Device Token, Mobile PANToken, associated with a Mobile PAN. Tokens and Mobile PAN can besecurely stored on device file system or into a Secure Element (SE)comprised within the device. During the registration process, AccountOwner can register one or more biometric factors to be used inconnection with accounts and transactions. These biometric factors maybe stored locally on the device or biometric factors may be transmittedto the SPCD. Locally stored biometric factors can be stored on devicefile system or into a Secure Element comprised within the device. Atoken can be associated with each stored biometric factor, stored on thedevice SE and transmitted to the SPCD. For additional security and toprevent a secure element from being moved to another device, a uniqueidentifier such as an IMEI or Serial No. can be derived from the device,hashed, and stored within the Secure Element comprised within thedevice.

FIG. 68 illustrates an exemplary registration flow sponsored by thecredit reporting bureau. Credit reporting bureau (68.20) using list ofall credit reporting accounts (68.10) sends communication with offer toregister credit reporting account to Account Owners (68.30). In step(68.40) Account Owners may register credit reporting account to bestored in Database (68.50). In the process of registering the creditreporting Account (68.50), Account Owner may also register PIN numbers,Mobile Devices, Wearable Devices, Lenders, Banks and other informationrelated to the registered credit reporting account and as previouslydescribed in the Figures and exemplary tables. As shown, Mobile Device(68.90) is comprised of Registration Application (68.99) which is usedto create New Devices Database (68.80). Registration Application may bestored within Secure Element (SE). All new registration data is storedinto SPCD database (68.70). Registered account numbers may betransmitted by credit reporting agency to other entities such as banks,lenders upon the registration of a mobile device. During the deviceregistration process one or more tokens may be generated by the SPCD andtransmitted to the Mobile Device. Tokens may include a Device Token,Mobile PAN Token associated with a Mobile PAN. Tokens and Mobile PAN canbe securely stored on device file system or into a Secure Elementcomprised within the device. During the registration process, AccountOwner can register one or more biometric factors to be used inconnection with accounts and transactions. These biometric factors maybe stored locally on the device or biometric factors may be transmittedto the SPCD. Locally stored biometric factors can be stored on devicefile system or into a Secure Element (SE) comprised within the device. Atoken can be associated with each stored biometric factor, stored on thedevice SE and transmitted to the SPCD. For additional security and toprevent a secure element from being moved to another device, a uniqueidentifier such as an IMEI or Serial No. can be derived from the device,hashed, and stored within the Secure Element comprised within thedevice.

It should be noted that the database tables described herein areexemplary based on the described functions of the SPCD. For performancereasons or other design considerations, these tables may be combinedtogether or further decomposed into normalized views.

It should be noted that the authentication methods and steps describedherein for POS, ATM and eCommerce transactions may be used in otherpayment and non-payment transactions such as health record releaseapproval, credit record release approval, and other approval flows whichrequire a consumer to authenticate the release or use of privateinformation.

For example, referring now to FIG. 69, Registered User [6901] using stepA completes Credit Application [6902] which is submitted using step B toCredit Issuer [6903]. Credit Issuer may be one of a Bank, Merchant,Automobile Dealership, or other credit granting entity. Credit Issuersubmits the Credit Application to the Credit Bureau [6904] using step C.Credit Bureau using Tables [6905] determines if the Registered User haspreviously registered their credit account for mobile authentication. Ifthe credit account has been registered [as previously described in FIG.68], the Credit Bureau notifies the SPCD [6906] (now operable as aSecure Processor Computing Device for non-payment transaction) usingstep D that a credit report has been requested for the Registered User.Upon receiving the request, the SPCD accesses the Registered User'sinformation stored in SPCD Tables (6907). Upon determining theregistered mobile device associated with this credit account, anauthentication request [6908] is sent to the registered mobile device[6909]. Upon receiving the authentication request, Registered User[6901] provides the requested PIN and/or Biometric data into theregistered mobile device. The authentication response can be comprisedof a first token associated with the credit report of the registereduser and a second token associated with the registered mobile device.Mobile device is operable to transmit an authentication response [6912]in accordance with the configuration requirements. Message [6912] mayinclude one or more of PIN, Biometric, Token, and Location. SPCD isoperable to receive the authentication response and validate theinformation comprised within the response in accordance withconfiguration requirements. Upon a successful authentication, SPCD sendsan approval message to the Credit Bureau [6903] using step E. CreditBureau releases the Credit Report to Credit Issuer [6903] using step F.

In another example, referring now to FIG. 70, Registered User [7001]using step A completes Insurance Application [7002] which is submittedusing step B to Insurance Company [7003]. Insurance Company be one of aHealth, Disability, or other insurance provider that may have a need formedical records. Insurance Company submits the Insurance Application tothe Medical Record Entity [7004] using step C. The Medical Record Entitymay be any authorized holder of medical records such as a hospital.Medical Record entity using Tables [7005] determines if the RegisteredUser has previously registered their medical record accounts for mobileauthentication. If the medical record account has been registered [aspreviously described in FIGS. 66], the Medical Record entity notifiesthe SPCD [7006] (now operable as a Secure Processor Computing Device fornon-payment transaction) using step D that a medical record has beenrequested for the Registered User. Upon receiving the request, the SPCDaccesses the Registered User's information stored in SPCD Tables (7007).Upon determining the registered mobile device associated with thismedical record account, an authentication request [7008] is sent to theregistered mobile device [7009]. Upon receiving the authenticationrequest, Registered User [7001] provides the requested PIN and/orBiometric data into the registered mobile device. Mobile device isoperable to transmit an authentication response [7012] in accordancewith the configuration requirements. Message [7012] may include one ormore of PIN, Biometric, Token, and Location. The authentication responsecan be comprised of a first token associated with the medical record ofthe registered user and a second token associated with the registeredmobile device. SPCD is operable to receive the authentication responseand validate the information comprised within the response in accordancewith configuration requirements. Upon a successful authentication, SPCDsends an approval message to the Medical Record entity [7003] using stepE. Medical Record entity releases the medical record to InsuranceCompany [7003] using step F.

In another example, referring now to FIG. 71, Registered User (aspatient) [7101] using step A engages with Doctor [7102] which requestsmedical records using step B from Healthcare Provider [7103]. HealthcareProvider be one of a Hospital, Clinic, or other provider that may have aneed for medical records such as a laboratory. Healthcare Providersubmits the request to the Medical Record Entity [7104] using step C.The Medical Record Entity may be any authorized holder of medicalrecords such as a hospital or another central EMR system. Medical Recordentity using Tables [7105] determines if the Registered User haspreviously registered their medical record accounts for mobileauthentication. If the medical record account has been registered [aspreviously described in FIGS. 66], the Medical Record entity notifiesthe SPCD [7106] (now operable as a Secure Processor Computing Device fornon-payment transaction) using step D that a medical record has beenrequested for the Registered User. Upon receiving the request, the SPCDaccesses the Registered User's information stored in SPCD Tables (7107).Upon determining the registered mobile device associated with thismedical record account, an authentication request [7108] is sent to theregistered mobile device [7109]. Upon receiving the authenticationrequest, Registered User [7101] provides the requested PIN and/orBiometric data into the registered mobile device. Mobile device isoperable to transmit an authentication response [7112] in accordancewith the configuration requirements. Message [7112] may include one ormore of PIN, Biometric, Token, and Location. The authentication responsecan be comprised of a first token associated with the medical record ofthe registered user and a second token associated with the registeredmobile device. SPCD is operable to receive the authentication responseand validate the information comprised within the response in accordancewith configuration requirements. Upon a successful authentication, SPCDsends an approval message to the Medical Record entity [7103] using stepE. Medical Record entity releases the medical record to InsuranceCompany [7103] using step F.

FIG. 72 describes an algorithm for coding and decoding a dynamic mobilePAN number associated with a payment transaction. Mobile Device [7200]has been previously configured and is comprised of a Secure Element[7210]. Secure Element is further comprised of Applet [7220], RandomSeed [7225], Sequence No. [7230], Device Token [7235], Mobile PAN Token[7240], Static Mobile PAN [7245], and Dynamic Mobile PAN [7250]. SecureElement [7210] may also store Hashed IMEI or Serial No. [7265] which canbe read from IMEI or Serial No. stored on device. Applet [7220] isoperable to increment Sequence Number [7230] and request a next RandomSeed from the SPCD [7280]. The request for the Random Seed value is madeusing the Device Token [7235] and the Sequence Number [7230]. The SPCDDynamic PAN Module [7285] is operable to validate the Device Token[7235] in conjunction with the Sequence Number [7230]. If there are nogaps in sequence numbers for this device token, the Dynamic PAN Module[7285] is operable to generate a new random seed value and transmit thenew random seed value to the Mobile Device [7200]. New seed value isstored in the Secure Element [7210] of the mobile device by Applet[7220] and also stored on the SPCD as Random Seed [7291] associated withthe Device Token. Applet [7220] is operable to generate a Dynamic MobilePAN [7250] using the previously stored Static Mobile PAN [7245] hashedwith the Random Seed [7225]. Contemporaneously with the processing onthe mobile device, the Dynamic PAN Module [7285] is operable to lookupthe Static Mobile PAN [7295] number (see FIG. 56) associated with theDevice Token [7235] and using Random Seed value [7291], generate aDerived Mobile PAN [7296]. Derived Mobile PAN [7296] can be stored as acolumn in the Mobile PAN, Device, Mobile PIN Table (FIG. 56) andassociated with the Mobile PAN comprised within this table for theMobile Device [7200]. The Derived Dynamic Mobile PAN serves as analternate key which can be used by the SPCD during payment transactions.The algorithm described herein for dynamic Mobile PANs associated withpayment accounts may be equally applied to accounts associated withhealth records and credit reports.

FIG. 73 describes the ecosystem and participants comprised of aplurality of consumers, merchants, banks, insurance companies,healthcare providers, credit reporting agencies, payment processors, andmobile devices; each participant and device registered within a SecureProcessor Computing Device [7301] which is further comprised of programlogic, database tables and configuration settings that store informationabout the participants and constitute the criteria by which theecosystem participants and devices access and transact with the SecureProcessor Computing Device.

FIG. 74 describes a Common Transaction Authentication Flow that can beshared with payment and non-payment use cases described herein. Forexample the following general steps are applicable for any transactionthat requires an out-of-band authentication related to the disclosure ofsensitive data or for a sensitive transaction such as a paymenttransaction:

Receive transaction [7401]Determine device (7402]

Send Authentication Request [7403] Receive Authentication Response[7404] Evaluate Authentication Response [7405] Determine if Criteria aremet [7406]

Approve transaction in accordance with Criteria [7407]

FIG. 75 illustrates a Biometric Device Hub and a variety of wearablesoperable to receive inputs and communicate data to other devices andcomponents. For example, Mobile Device (75.10) is in communication withSecure Payment Computing Device (SPCD) (75.60) and is comprised of a BioSignal Handler module (75.50). Mobile Device (75.10) is operable toreceive and securely store biometric data received from connecteddevices and serves as a hub to transmit aggregated biometric data to theSPCD (75.60). For example, Biometric ring (75.20) may be operable toread a body temperature and transmit body temperature reading to mobiledevice (75.10) using BLE or other protocol. Or alternatively, biometriceyeglasses (75.40) may be operable to read an iris scan and transmit ascanned image to mobile device (75.10) using BLE or other protocol. Or,alternatively, biometric watch (75.30) may be operable to read a heartrate and transmit heart rate information to mobile device (75.10), usingBLE or other protocol. Mobile device (75.10) may also be operable todirectly receive voice (75.110) and finger print (75.100) biometricdata. As biometric data is received from the Bio Signal Handler (75.50)data is encrypted and stored in the Encrypted Bio Data file system(75.60). The Encrypted Bio Data file system may be a SQLite Db orsimilar Db that can be encrypted and embodied on a mobile device. MobileDevice (75.10) may receive a Biometric Data Request message (75.150)from the SPCD (75.10). Biometric Data Handler (75.70) reads EncryptedBio Data (75.60) to retrieve available biometric data and transmit tothe SPCD (75.60) using Aggregated Biometric Data (75.160). All Biosignals are received by the bio signal handling module and forwarded asaggregated biometric data to the SPCD in accordance with transactionauthentication requirements. Wearable devices may also be operable totransmit data using WiFi or cellular communications and communicatedirectly with the SPCD. As prescribed by the Setting (75.80) andDatabase (75.90), a request for one or more of a fingerprint, heartrate, body temperature, iris scan, and voice print may be required.

The methods described herein for authenticating payment transactions maybe applied to the authentication of non-payment transaction related tocredit and healthcare records as well as other forms of confidentialdata such as Personally Identifiable Data (PII) and Corporate Data.

1-23. (canceled)
 24. A method for processing a secure mobile paymenttransaction conducted at a location of a merchant comprising: receiving,from a point-of-sale device at the location of a merchant, mobilepayment data that is associated with the secure mobile paymenttransaction, which is initiated after a registration event, andcomprising a payment account number transmitted from a registered mobiledevice of a consumer; transmitting, from a mobile wallet system to theregistered mobile device, an approval request; receiving, at the mobilewallet system from the registered mobile device of the consumer, anindication indicating the consumer has approved the secure mobilepayment transaction; analyzing, by the mobile wallet system, the mobilepayment data received from the point-of-sale device to identify themobile payment data as comprising the payment account number; uponidentifying the mobile payment data as comprising the payment accountnumber, receiving, at a secure payment computing device, the paymentaccount number associated with the secure mobile payment transaction;determining, by the secure payment computing, device, mobile deviceinformation associated with the payment account number; sending anauthentication request from the secure payment computing device to theregistered mobile device; receiving, at the secure payment computingdevice from the registered mobile device, an authentication response,the authentication response comprising biometric-related informationindicating that a registered user has approved the payment, transaction.using at least one or more fingerprint biometric factors correspondingto a fingerprint captured contemporaneously when the registered usertouches a position on a user interface of the registered mobile device,the fingerprint biometric factors received by a biometric signal handlerof the registered mobile device and validated on the mobile device bycomparing the one or more fingerprint biometric factors to previouslyregistered fingerprint biometric factors stored on a file system orsecure element of the mobile device, wherein a first fingerprintbiometric factor is captured when the registered user's first fingertouches a position of the user interface; authenticating the transactionbased on biometric-related information received at the secure paymentcomputing device matching previously stored information at the securepayment computing device; in response to authenticating the transaction,transmitting at least a portion of the mobile payment data to a securepayment network for processing; and after transmitting the mobilepayment data to the secure payment network for processing, transmitting,by the mobile wallet system, a payment confirmation to the point-of-saledevice at the location of the merchant.
 25. The computer-implementedmethod of claim 24 wherein the payment account number is transmitted tothe point-of-sale device from a registered mobile device of a consumer.26. The computer-implemented method of claim 24, further comprisingreceiving, at a web server of the mobile wallet system from theconsumer, in connection with the registration event that is completedprior to the secure mobile payment transaction, the informationassociated with a mobile device of the consumer.
 27. Thecomputer-implemented method of claim 24, determining, by the securepayment computing device, the mobile device information associated withthe payment account number comprises determining the mobile deviceinformation associated with the payment account number using a databasetable.
 28. The computer-implemented method of claim 27, wherein thedatabase table comprises rules and settings that establish a criteriaused in authenticating the payment transaction.
 29. Thecomputer-implemented method of claim 24, wherein the criteria includes aprescribed biometric correlation sequence.
 30. The computer-implementedmethod of claim of claim 24, further comprising, upon identifying themobile payment data as comprising the payment account number,determining, based on a selection from the consumer, information fromthe registration event, and using the information in completing thesecure mobile payment transaction.
 31. The computer-implemented methodof claim 24, wherein the payment account number is issued to theregistered mobile device after the registration process.
 32. Thecomputer-implemented method of claim 24, wherein information generatedas part of the registration process is stored on the registered mobiledevice.
 33. The computer-implemented method of claim 24, whereininformation generated as part of the registration process is stored in asecure element of the registered mobile device.
 34. An e-commerceenvironment for processing a secure mobile payment transaction conductedat a oration of a merchant comprising: a secure payment computing devicehaving a web server having a network interface for receiving andprocessing information received from Internet sources in connection withthe registration event; a transaction gateway for receiving andprocessing payment transactions; a messaging server having a networkinterface for communicating with a registered mobile device that becameregistered as part of the registration event, and a database for storingsettings from one or more of a merchant, an issuer, a payment network, apayment acquirer, and an e-commerce gateway; a mobile wallet systemcommunicably coupled to the secure payment computing device communicablycoupled to the mobile wallet system, wherein the mobile wallet system isoperable to receive, from a point-of-sale device at the location of amerchant, mobile payment data that is associated with the secure mobilepayment transaction, which is initiated after a registration event,wherein the mobile payment data comprises a payment account numbertransmitted from a registered mobile device of a consumer, transmit, tothe registered mobile device, an approval request, receive, from theregistered mobile device of the consumer, an indication indicating theconsumer has approved the secure mobile payment transaction, and analyzethe mobile payment data received from the point-of-sale device toidentify the mobile payment data as comprising the payment accountnumber; upon identifying the mobile payment data as comprising thepayment account number, the secure payment computing device is operableto: receive the payment account number associated with the secure mobilepayment transaction, determine mobile device information associated withthe payment account number, send an authentication request to theregistered mobile device, and receive, from the registered mobiledevice, an authentication response, the authentication responsecomprising biometric-related information indicating that a registereduser has approved the payment transaction using at least one or morefingerprint biometric factors corresponding to a fingerprint capturedcontemporaneously when the registered user touches a position on a userinterface of the registered mobile device, the fingerprint biometricfactors received by a biometric signal handler of the registered mobiledevice and validated on the mobile device by comparing the one or morefingerprint biometric factors to previously registered fingerprintbiometric factors stored on a file system or secure element of themobile device, wherein a first fingerprint biometric factor is capturedwhen the registered user's first finger touches a position of the userinterface, authenticate the transaction based on biometric-relatedinformation received at the secure payment computing device matchingpreviously stored information at the secure payment computing device, inresponse to authenticating the transaction, transmit at least a portionof the mobile payment data to a secure payment network for processing;and wherein after transmitting the mobile payment data to the securepayment network for processing, the mobile wallet system is operable totransmit a payment confirmation to the point-of-sale device at thelocation of the merchant.
 35. The e-commerce environment of claim 34wherein the payment account number is transmitted to the point-of-saledevice from a registered mobile device of a consumer.
 36. The e-commerceenvironment of claim 34, further comprising receiving, at a web serverof the mobile wallet system from the consumer, in connection with theregistration event that is completed prior to the secure mobile paymenttransaction, the information associated with a mobile device of theconsumer.
 37. The e-commerce environment of claim 34, determining, bythe secure payment computing device, the mobile device informationassociated with the payment account number comprises determining themobile device information associated with the payment account numberusing a database table.
 38. The e-commerce environment of claim 35,wherein the database table comprises rules and settings that establish acriteria used in authenticating the payment transaction.
 39. Thee-commerce environment of claim 34, wherein the criteria includes aprescribed biometric correlation sequence.
 40. The e-commerceenvironment of claim 34, further comprising, upon identifying the mobilepayment data as comprising the payment account number, determining,based on a selection from the consumer, information from theregistration event, and using the information in completing the securemobile payment transaction.
 41. The e-commerce environment of claim 34,wherein the payment account number is issued to the registered mobiledevice after the registration process.
 42. The e-commerce environment ofclaim 34, wherein information generated as part of the registrationprocess is stored on the registered mobile device.
 43. The e-commerceenvironment of claim 34, wherein information generated as part of theregistration process is stored in a secure element of the registeredmobile device.